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://zeroday.forem.com/privacy#c-information-collected-from-other-sources | Privacy Policy - Security Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Security Forem Close 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 Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:49:04 |
https://policies.python.org/python.org/code-of-conduct/#transparency-reports | Python Software Foundation Code of Conduct - Python Software Foundation Policies Skip to content Python Software Foundation Policies Python Software Foundation Code of Conduct GitHub Python Software Foundation Policies GitHub PSF Privacy Notice pypi.org pypi.org Terms of Service Acceptable Use Policy Privacy Notice Code of Conduct Superseded Superseded Terms of Use python.org python.org CVE Numbering Authority Contributing Copyright Policy Legal Statements Privacy Notice Code of Conduct Code of Conduct Python Software Foundation Code of Conduct Python Software Foundation Code of Conduct Table of contents Our Community Our Standards Inappropriate Behavior Weapons Policy Consequences Scope PSF Events PSF Online Spaces Contact Information Procedure for Handling Incidents License Transparency Reports Attributions Best practices guide for a Code of Conduct for events Python Software Foundation Code of Conduct Working Group Enforcement Procedures Python Software Foundation Community Member Procedure For Reporting Code of Conduct Incidents Releasing a Good Conference Transparency Report us.pycon.org us.pycon.org Privacy Notice Code of Conduct Code of Conduct PyCon US Code of Conduct PyCon US Code of Conduct Enforcement Procedures PyCon US Procedures for Reporting Code of Conduct Incidents Reference Reference SSDF Request Response Table of contents Our Community Our Standards Inappropriate Behavior Weapons Policy Consequences Scope PSF Events PSF Online Spaces Contact Information Procedure for Handling Incidents License Transparency Reports Attributions Python Software Foundation Code of Conduct The Python community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences great successes and continued growth. When you're working with members of the community, this Code of Conduct will help steer your interactions and keep Python a positive, successful, and growing community. Our Community Members of the Python community are open, considerate, and respectful . Behaviours that reinforce these values contribute to a positive environment, and include: Being open. Members of the community are open to collaboration, whether it's on PEPs, patches, problems, or otherwise. Focusing on what is best for the community. We're respectful of the processes set forth in the community, and we work within them. Acknowledging time and effort. We're respectful of the volunteer efforts that permeate the Python community. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community. Being respectful of differing viewpoints and experiences. We're receptive to constructive comments and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. Showing empathy towards other community members. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views. Being considerate. Members of the community are considerate of their peers -- other Python users. Being respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. Gracefully accepting constructive criticism. When we disagree, we are courteous in raising our issues. Using welcoming and inclusive language. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference. Our Standards Every member of our community has the right to have their identity respected. The Python community is dedicated to providing a positive experience for everyone, regardless of age, gender identity and expression, sexual orientation, disability, physical appearance, body size, ethnicity, nationality, race, or religion (or lack thereof), education, or socio-economic status. Inappropriate Behavior Examples of unacceptable behavior by participants include: Harassment of any participants in any form Deliberate intimidation, stalking, or following Logging or taking screenshots of online activity for harassment purposes Publishing others' private information, such as a physical or electronic address, without explicit permission Violent threats or language directed against another person Incitement of violence or harassment towards any individual, including encouraging a person to commit suicide or to engage in self-harm Creating additional online accounts in order to harass another person or circumvent a ban Sexual language and imagery in online communities or in any conference venue, including talks Insults, put downs, or jokes that are based upon stereotypes, that are exclusionary, or that hold others up for ridicule Excessive swearing Unwelcome sexual attention or advances Unwelcome physical contact, including simulated physical contact (eg, textual descriptions like "hug" or "backrub") without consent or after a request to stop Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others Sustained disruption of online community discussions, in-person presentations, or other in-person events Continued one-on-one communication after requests to cease Other conduct that is inappropriate for a professional audience including people of many different backgrounds Community members asked to stop any inappropriate behavior are expected to comply immediately. Weapons Policy No weapons are allowed at Python Software Foundation events. Weapons include but are not limited to explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. Consequences If a participant engages in behavior that violates this code of conduct, the Python community Code of Conduct team may take any action they deem appropriate, including warning the offender or expulsion from the community and community events with no refund of event tickets. The full list of consequences for inappropriate behavior is listed in the Enforcement Procedures . Thank you for helping make this a welcoming, friendly community for everyone. Scope PSF Events This Code of Conduct applies to the following people at events hosted by the Python Software Foundation, and events hosted by projects under the PSF's fiscal sponsorship : staff Python Software Foundation board members speakers panelists tutorial or workshop leaders poster presenters people invited to meetings or summits exhibitors organizers volunteers all attendees The Code of Conduct applies in official venue event spaces, including: exhibit hall or vendor tabling area panel and presentation rooms hackathon or sprint rooms tutorial or workshop rooms poster session rooms summit or meeting rooms staff areas con suite meal areas party suites walkways, hallways, elevators, and stairs that connect any of the above spaces The Code of Conduct applies to interactions with official event accounts on social media spaces and phone applications, including: comments made on official conference phone apps comments made on event video hosting services comments made on the official event hashtag or panel hashtags Event organizers will enforce this code throughout the event. Each event is required to provide a Code of Conduct committee that receives, evaluates, and acts on incident reports. Each event is required to provide contact information for the committee to attendees. The event Code of Conduct committee may (but is not required to) ask for advice from the Python Software Foundation Code of Conduct work group. The Python Software Foundation Code of Conduct work group can be reached by emailing conduct-wg@python.org . PSF Online Spaces This Code of Conduct applies to the following online spaces: Mailing lists, including docs , core-mentorship and all other mailing lists hosted on python.org Core developers' Python Discord server The PSF Discord and Slack servers Python Software Foundation hosted Discourse server discuss.python.org Code repositories, issue trackers, and pull requests made against any Python Software Foundation-controlled GitHub organization Any other online space administered by the Python Software Foundation This Code of Conduct applies to the following people in official Python Software Foundation online spaces: PSF Members, including Fellows admins of the online space maintainers reviewers contributors all community members Each online space listed above is required to provide the following information to the Python Software Foundation Code of Conduct work group: contact information for any administrators/moderators Each online space listed above is encouraged to provide the following information to community members: a welcome message with a link to this Code of Conduct and the contact information for making an incident report conduct-wg@python.org The Python Software Foundation Code of Conduct work group will receive and evaluate incident reports from the online communities listed above. The Python Software Foundation Code of Conduct work group will work with online community administrators/moderators to suggest actions to take in response to a report. In cases where the administrators/moderators disagree on the suggested resolution for a report, the Python Software Foundation Code of Conduct work group may choose to notify the Python Software Foundation board. Contact Information If you believe that someone is violating the code of conduct, or have any other concerns, please contact a member of the Python Software Foundation Code of Conduct work group immediately. They can be reached by emailing conduct-wg@python.org Procedure for Handling Incidents Python Software Foundation Community Member Procedure For Reporting Code of Conduct Incidents Python Software Foundation Code of Conduct Working Group Enforcement Procedures License This Code of Conduct is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License . Transparency Reports 2024 Transparency Report Attributions This Code of Conduct was forked from the example policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers , which is under a Creative Commons Zero license . Additional new language and modifications were created by Sage Sharp of Otter Tech . Language was incorporated from the following Codes of Conduct: Affect Conf Code of Conduct , licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License . Citizen Code of Conduct , licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License . Contributor Covenant version 1.4 , licensed Creative Commons Attribution 4.0 License . Django Project Code of Conduct , licensed under a Creative Commons Attribution 3.0 Unported License . LGBTQ in Tech Slack Code of Conduct , licensed under a Creative Commons Zero License . PyCon 2018 Code of Conduct , licensed under a Creative Commons Attribution 3.0 Unported License . Rust Code of Conduct November 24, 2025 Made with Material for MkDocs | 2026-01-13T08:49:04 |
https://future.forem.com/privacy#c-information-collected-from-other-sources | Privacy Policy - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:04 |
https://peps.python.org#index-by-category | PEP 0 – Index of Python Enhancement Proposals (PEPs) | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 0 Toggle light / dark / auto colour theme PEP 0 – Index of Python Enhancement Proposals (PEPs) Author : The PEP Editors Status : Active Type : Informational Created : 13-Jul-2000 Table of Contents Introduction Topics API Numerical Index Index by Category Process and Meta-PEPs Other Informational PEPs Provisional PEPs (provisionally accepted; interface may still change) Accepted PEPs (accepted; may not be implemented yet) Open PEPs (under consideration) Finished PEPs (done, with a stable interface) Historical Meta-PEPs and Informational PEPs Deferred PEPs (postponed pending further research or updates) Rejected, Superseded, and Withdrawn PEPs Reserved PEP Numbers PEP Types Key PEP Status Key Authors/Owners Introduction This PEP contains the index of all Python Enhancement Proposals, known as PEPs. PEP numbers are assigned by the PEP editors, and once assigned are never changed. The version control history of the PEP texts represent their historical record. Topics PEPs for specialist subjects are indexed by topic . Governance PEPs Packaging PEPs Release PEPs Typing PEPs API The PEPS API is a JSON file of metadata about all the published PEPs. Read more here . Numerical Index The numerical index contains a table of all PEPs, ordered by number. Index by Category Process and Meta-PEPs PEP Title Authors PA 1 PEP Purpose and Guidelines Barry Warsaw, Jeremy Hylton, David Goodger, Alyssa Coghlan PA 2 Procedure for Adding New Modules Brett Cannon, Martijn Faassen PA 4 Deprecation of Standard Modules Brett Cannon, Martin von Löwis PA 7 Style Guide for C Code Guido van Rossum, Barry Warsaw PA 8 Style Guide for Python Code Guido van Rossum, Barry Warsaw, Alyssa Coghlan PA 10 Voting Guidelines Barry Warsaw PA 11 CPython platform support Martin von Löwis, Brett Cannon PA 12 Sample reStructuredText PEP Template David Goodger, Barry Warsaw, Brett Cannon PA 13 Python Language Governance The Python core team and community PA 387 Backwards Compatibility Policy Benjamin Peterson PA 545 Python Documentation Translations Julien Palard, Inada Naoki, Victor Stinner PA 602 Annual Release Cycle for Python Łukasz Langa 3.9 PA 609 Python Packaging Authority (PyPA) Governance Dustin Ingram, Pradyun Gedam, Sumana Harihareswara PA 676 PEP Infrastructure Process Adam Turner PA 729 Typing governance process Jelle Zijlstra, Shantanu Jain PA 731 C API Working Group Charter Guido van Rossum, Petr Viktorin, Victor Stinner, Steve Dower, Irit Katriel PA 732 The Python Documentation Editorial Board Joanna Jablonski PA 761 Deprecating PGP signatures for CPython artifacts Seth Michael Larson 3.14 PA 811 Defining Python Security Response Team membership and responsibilities Seth Michael Larson Other Informational PEPs PEP Title Authors IA 20 The Zen of Python Tim Peters IA 101 Doing Python Releases 101 Barry Warsaw, Guido van Rossum IF 247 API for Cryptographic Hash Functions A.M. Kuchling IF 248 Python Database API Specification v1.0 Greg Stein, Marc-André Lemburg IF 249 Python Database API Specification v2.0 Marc-André Lemburg IA 257 Docstring Conventions David Goodger, Guido van Rossum IF 272 API for Block Encryption Algorithms v1.0 A.M. Kuchling IA 287 reStructuredText Docstring Format David Goodger IA 290 Code Migration and Modernization Raymond Hettinger IF 333 Python Web Server Gateway Interface v1.0 Phillip J. Eby IA 394 The “python” Command on Unix-Like Systems Kerrick Staley, Alyssa Coghlan, Barry Warsaw, Petr Viktorin, Miro Hrončok, Carol Willing IF 399 Pure Python/C Accelerator Module Compatibility Requirements Brett Cannon 3.3 IF 430 Migrating to Python 3 as the default online documentation Alyssa Coghlan IA 434 IDLE Enhancement Exception for All Branches Todd Rovito, Terry Reedy IF 452 API for Cryptographic Hash Functions v2.0 A.M. Kuchling, Christian Heimes IF 457 Notation For Positional-Only Parameters Larry Hastings IF 482 Literature Overview for Type Hints Łukasz Langa IF 483 The Theory of Type Hints Guido van Rossum, Ivan Levkivskyi IA 514 Python registration in the Windows registry Steve Dower IF 579 Refactoring C functions and methods Jeroen Demeyer IF 588 GitHub Issues Migration Plan Mariatta IF 607 Reducing CPython’s Feature Delivery Latency Łukasz Langa, Steve Dower, Alyssa Coghlan 3.9 IA 619 Python 3.10 Release Schedule Pablo Galindo Salgado 3.10 IF 630 Isolating Extension Modules Petr Viktorin IF 635 Structural Pattern Matching: Motivation and Rationale Tobias Kohn, Guido van Rossum 3.10 IF 636 Structural Pattern Matching: Tutorial Daniel F Moisset 3.10 IF 659 Specializing Adaptive Interpreter Mark Shannon IA 664 Python 3.11 Release Schedule Pablo Galindo Salgado 3.11 IA 672 Unicode-related Security Considerations for Python Petr Viktorin IA 693 Python 3.12 Release Schedule Thomas Wouters 3.12 IA 719 Python 3.13 Release Schedule Thomas Wouters 3.13 IF 733 An Evaluation of Python’s Public C API Erlend Egeberg Aasland, Domenico Andreoli, Stefan Behnel, Carl Friedrich Bolz-Tereick, Simon Cross, Steve Dower, Tim Felgentreff, David Hewitt, Shantanu Jain, Wenzel Jakob, Irit Katriel, Marc-Andre Lemburg, Donghee Na, Karl Nelson, Ronald Oussoren, Antoine Pitrou, Neil Schemenauer, Mark Shannon, Stepan Sindelar, Gregory P. Smith, Eric Snow, Victor Stinner, Guido van Rossum, Petr Viktorin, Carol Willing, William Woodruff, David Woods, Jelle Zijlstra IA 745 Python 3.14 Release Schedule Hugo van Kemenade 3.14 IF 762 REPL-acing the default REPL Pablo Galindo Salgado, Łukasz Langa, Lysandros Nikolaou, Emily Morehouse-Valcarcel 3.13 IA 790 Python 3.15 Release Schedule Hugo van Kemenade 3.15 IA 801 Reserved Barry Warsaw IF 3333 Python Web Server Gateway Interface v1.0.1 Phillip J. Eby IF 8000 Python Language Governance Proposal Overview Barry Warsaw IF 8002 Open Source Governance Survey Barry Warsaw, Łukasz Langa, Antoine Pitrou, Doug Hellmann, Carol Willing IA 8016 The Steering Council Model Nathaniel J. Smith, Donald Stufft IF 8100 January 2019 Steering Council election Nathaniel J. Smith, Ee Durbin IF 8101 2020 Term Steering Council election Ewa Jodlowska, Ee Durbin IF 8102 2021 Term Steering Council election Ewa Jodlowska, Ee Durbin, Joe Carey IF 8103 2022 Term Steering Council election Ewa Jodlowska, Ee Durbin, Joe Carey IF 8104 2023 Term Steering Council election Ee Durbin IF 8105 2024 Term Steering Council election Ee Durbin IF 8106 2025 Term Steering Council election Ee Durbin IF 8107 2026 Term Steering Council election Ee Durbin Provisional PEPs (provisionally accepted; interface may still change) PEP Title Authors SP 708 Extending the Repository API to Mitigate Dependency Confusion Attacks Donald Stufft Accepted PEPs (accepted; may not be implemented yet) PEP Title Authors SA 458 Secure PyPI downloads with signed repository metadata Trishank Karthik Kuppusamy, Vladimir Diaz, Marina Moore, Lukas Puehringer, Joshua Lock, Lois Anne DeLong, Justin Cappos SA 658 Serve Distribution Metadata in the Simple Repository API Tzu-ping Chung SA 668 Marking Python base environments as “externally managed” Geoffrey Thomas, Matthias Klose, Filipe Laíns, Donald Stufft, Tzu-ping Chung, Stefano Rivera, Elana Hashman, Pradyun Gedam SA 686 Make UTF-8 mode default Inada Naoki 3.15 SA 687 Isolating modules in the standard library Erlend Egeberg Aasland, Petr Viktorin 3.12 SA 691 JSON-based Simple API for Python Package Indexes Donald Stufft, Pradyun Gedam, Cooper Lees, Dustin Ingram SA 699 Remove private dict version field added in PEP 509 Ken Jin 3.12 SA 701 Syntactic formalization of f-strings Pablo Galindo Salgado, Batuhan Taskaya, Lysandros Nikolaou, Marta Gómez Macías 3.12 SA 703 Making the Global Interpreter Lock Optional in CPython Sam Gross 3.13 SA 714 Rename dist-info-metadata in the Simple API Donald Stufft SA 728 TypedDict with Typed Extra Items Zixuan James Li 3.15 SA 739 build-details.json 1.0 — a static description file for Python build details Filipe Laíns 3.14 SA 753 Uniform project URLs in core metadata William Woodruff, Facundo Tuesca SA 770 Improving measurability of Python packages with Software Bill-of-Materials Seth Larson SA 773 A Python Installation Manager for Windows Steve Dower SA 793 PyModExport: A new entry point for C extension modules Petr Viktorin 3.15 SA 794 Import Name Metadata Brett Cannon SA 798 Unpacking in Comprehensions Adam Hartz, Erik Demaine 3.15 SA 799 A dedicated profiling package for organizing Python profiling tools Pablo Galindo Salgado, László Kiss Kollár 3.15 SA 810 Explicit lazy imports Pablo Galindo Salgado, Germán Méndez Bravo, Thomas Wouters, Dino Viehland, Brittany Reynoso, Noah Kim, Tim Stumbaugh 3.15 Open PEPs (under consideration) PEP Title Authors S 467 Minor API improvements for binary sequences Alyssa Coghlan, Ethan Furman 3.15 S 480 Surviving a Compromise of PyPI: End-to-end signing of packages Trishank Karthik Kuppusamy, Vladimir Diaz, Justin Cappos, Marina Moore S 603 Adding a frozenmap type to collections Yury Selivanov S 638 Syntactic Macros Mark Shannon S 653 Precise Semantics for Pattern Matching Mark Shannon S 671 Syntax for late-bound function argument defaults Chris Angelico 3.12 S 694 Upload 2.0 API for Python Package Indexes Barry Warsaw, Donald Stufft, Ee Durbin S 710 Recording the provenance of installed packages Fridolín Pokorný S 711 PyBI: a standard format for distributing Python Binaries Nathaniel J. Smith S 718 Subscriptable functions James Hilton-Balfe 3.15 I 720 Cross-compiling Python packages Filipe Laíns 3.12 S 725 Specifying external dependencies in pyproject.toml Pradyun Gedam, Jaime Rodríguez-Guerra, Ralf Gommers S 743 Add Py_OMIT_LEGACY_API to the Python C API Victor Stinner, Petr Viktorin 3.15 I 744 JIT Compilation Brandt Bucher, Savannah Ostrowski 3.13 S 746 Type checking Annotated metadata Adrian Garcia Badaracco 3.15 S 747 Annotating Type Forms David Foster, Eric Traut 3.15 S 748 A Unified TLS API for Python Joop van de Pol, William Woodruff 3.14 S 752 Implicit namespaces for package repositories Ofek Lev, Jarek Potiuk P 755 Implicit namespace policy for PyPI Ofek Lev S 764 Inline typed dictionaries Victorien Plot 3.15 I 766 Explicit Priority Choices Among Multiple Indexes Michael Sarahan S 767 Annotating Read-Only Attributes Eneg 3.15 S 771 Default Extras for Python Software Packages Thomas Robitaille, Jonathan Dekhtiar P 772 Packaging Council governance process Barry Warsaw, Deb Nicholson, Pradyun Gedam I 776 Emscripten Support Hood Chatham 3.14 S 777 How to Re-invent the Wheel Emma Harper Smith S 780 ABI features as environment markers Klaus Zimmermann, Ralf Gommers 3.14 S 781 Make TYPE_CHECKING a built-in constant Inada Naoki 3.15 S 783 Emscripten Packaging Hood Chatham S 785 New methods for easier handling of ExceptionGroups Zac Hatfield-Dodds 3.14 S 788 Protecting the C API from Interpreter Finalization Peter Bierma 3.15 S 789 Preventing task-cancellation bugs by limiting yield in async generators Zac Hatfield-Dodds, Nathaniel J. Smith 3.14 S 800 Disjoint bases in the type system Jelle Zijlstra 3.15 S 802 Display Syntax for the Empty Set Adam Turner 3.15 S 803 Stable ABI for Free-Threaded Builds Petr Viktorin 3.15 S 804 An external dependency registry and name mapping mechanism Pradyun Gedam, Ralf Gommers, Michał Górny, Jaime Rodríguez-Guerra, Michael Sarahan S 806 Mixed sync/async context managers with precise async marking Zac Hatfield-Dodds 3.15 S 807 Index support for Trusted Publishing William Woodruff S 808 Including static values in dynamic project metadata Henry Schreiner, Cristian Le S 809 Stable ABI for the Future Steve Dower 3.15 S 814 Add frozendict built-in type Victor Stinner, Donghee Na 3.15 S 815 Deprecate RECORD.jws and RECORD.p7s Konstantin Schütze, William Woodruff I 816 WASI Support Brett Cannon S 819 JSON Package Metadata Emma Harper Smith S 820 PySlot: Unified slot system for the C API Petr Viktorin 3.15 S 822 Dedented Multiline String (d-string) Inada Naoki 3.15 Finished PEPs (done, with a stable interface) PEP Title Authors SF 100 Python Unicode Integration Marc-André Lemburg 2.0 SF 201 Lockstep Iteration Barry Warsaw 2.0 SF 202 List Comprehensions Barry Warsaw 2.0 SF 203 Augmented Assignments Thomas Wouters 2.0 SF 205 Weak References Fred L. Drake, Jr. 2.1 SF 207 Rich Comparisons Guido van Rossum, David Ascher 2.1 SF 208 Reworking the Coercion Model Neil Schemenauer, Marc-André Lemburg 2.1 SF 214 Extended Print Statement Barry Warsaw 2.0 SF 217 Display Hook for Interactive Use Moshe Zadka 2.1 SF 218 Adding a Built-In Set Object Type Greg Wilson, Raymond Hettinger 2.2 SF 221 Import As Thomas Wouters 2.0 SF 223 Change the Meaning of x Escapes Tim Peters 2.0 SF 227 Statically Nested Scopes Jeremy Hylton 2.1 SF 229 Using Distutils to Build Python A.M. Kuchling 2.1 SF 230 Warning Framework Guido van Rossum 2.1 SF 232 Function Attributes Barry Warsaw 2.1 SF 234 Iterators Ka-Ping Yee, Guido van Rossum 2.1 SF 235 Import on Case-Insensitive Platforms Tim Peters 2.1 SF 236 Back to the __future__ Tim Peters 2.1 SF 237 Unifying Long Integers and Integers Moshe Zadka, Guido van Rossum 2.2 SF 238 Changing the Division Operator Moshe Zadka, Guido van Rossum 2.2 SF 250 Using site-packages on Windows Paul Moore 2.2 SF 252 Making Types Look More Like Classes Guido van Rossum 2.2 SF 253 Subtyping Built-in Types Guido van Rossum 2.2 SF 255 Simple Generators Neil Schemenauer, Tim Peters, Magnus Lie Hetland 2.2 SF 260 Simplify xrange() Guido van Rossum 2.2 SF 261 Support for “wide” Unicode characters Paul Prescod 2.2 SF 263 Defining Python Source Code Encodings Marc-André Lemburg, Martin von Löwis 2.3 SF 264 Future statements in simulated shells Michael Hudson 2.2 SF 273 Import Modules from Zip Archives James C. Ahlstrom 2.3 SF 274 Dict Comprehensions Barry Warsaw 2.7, 3.0 SF 277 Unicode file name support for Windows NT Neil Hodgson 2.3 SF 278 Universal Newline Support Jack Jansen 2.3 SF 279 The enumerate() built-in function Raymond Hettinger 2.3 SF 282 A Logging System Vinay Sajip, Trent Mick 2.3 SF 285 Adding a bool type Guido van Rossum 2.3 SF 289 Generator Expressions Raymond Hettinger 2.4 SF 292 Simpler String Substitutions Barry Warsaw 2.4 SF 293 Codec Error Handling Callbacks Walter Dörwald 2.3 SF 301 Package Index and Metadata for Distutils Richard Jones 2.3 SF 302 New Import Hooks Just van Rossum, Paul Moore 2.3 SF 305 CSV File API Kevin Altis, Dave Cole, Andrew McNamara, Skip Montanaro, Cliff Wells 2.3 SF 307 Extensions to the pickle protocol Guido van Rossum, Tim Peters 2.3 SF 308 Conditional Expressions Guido van Rossum, Raymond Hettinger 2.5 SF 309 Partial Function Application Peter Harris 2.5 SF 311 Simplified Global Interpreter Lock Acquisition for Extensions Mark Hammond 2.3 SF 318 Decorators for Functions and Methods Kevin D. Smith, Jim J. Jewett, Skip Montanaro, Anthony Baxter 2.4 SF 322 Reverse Iteration Raymond Hettinger 2.4 SF 324 subprocess - New process module Peter Astrand 2.4 SF 327 Decimal Data Type Facundo Batista 2.4 SF 328 Imports: Multi-Line and Absolute/Relative Aahz 2.4, 2.5, 2.6 SF 331 Locale-Independent Float/String Conversions Christian R. Reis 2.4 SF 338 Executing modules as scripts Alyssa Coghlan 2.5 SF 341 Unifying try-except and try-finally Georg Brandl 2.5 SF 342 Coroutines via Enhanced Generators Guido van Rossum, Phillip J. Eby 2.5 SF 343 The “with” Statement Guido van Rossum, Alyssa Coghlan 2.5 SF 352 Required Superclass for Exceptions Brett Cannon, Guido van Rossum 2.5 SF 353 Using ssize_t as the index type Martin von Löwis 2.5 SF 357 Allowing Any Object to be Used for Slicing Travis Oliphant 2.5 SF 358 The “bytes” Object Neil Schemenauer, Guido van Rossum 2.6, 3.0 SF 362 Function Signature Object Brett Cannon, Jiwon Seo, Yury Selivanov, Larry Hastings 3.3 SF 366 Main module explicit relative imports Alyssa Coghlan 2.6, 3.0 SF 370 Per user site-packages directory Christian Heimes 2.6, 3.0 SF 371 Addition of the multiprocessing package to the standard library Jesse Noller, Richard Oudkerk 2.6, 3.0 SF 372 Adding an ordered dictionary to collections Armin Ronacher, Raymond Hettinger 2.7, 3.1 SF 376 Database of Installed Python Distributions Tarek Ziadé 2.7, 3.2 SF 378 Format Specifier for Thousands Separator Raymond Hettinger 2.7, 3.1 SF 380 Syntax for Delegating to a Subgenerator Gregory Ewing 3.3 SF 383 Non-decodable Bytes in System Character Interfaces Martin von Löwis 3.1 SF 384 Defining a Stable ABI Martin von Löwis 3.2 SF 389 argparse - New Command Line Parsing Module Steven Bethard 2.7, 3.2 SF 391 Dictionary-Based Configuration For Logging Vinay Sajip 2.7, 3.2 SF 393 Flexible String Representation Martin von Löwis 3.3 SF 397 Python launcher for Windows Mark Hammond, Martin von Löwis 3.3 SF 405 Python Virtual Environments Carl Meyer 3.3 SF 409 Suppressing exception context Ethan Furman 3.3 SF 412 Key-Sharing Dictionary Mark Shannon 3.3 SF 414 Explicit Unicode Literal for Python 3.3 Armin Ronacher, Alyssa Coghlan 3.3 SF 415 Implement context suppression with exception attributes Benjamin Peterson 3.3 SF 417 Including mock in the Standard Library Michael Foord 3.3 SF 418 Add monotonic time, performance counter, and process time functions Cameron Simpson, Jim J. Jewett, Stephen J. Turnbull, Victor Stinner 3.3 SF 420 Implicit Namespace Packages Eric V. Smith 3.3 SF 421 Adding sys.implementation Eric Snow 3.3 SF 424 A method for exposing a length hint Alex Gaynor 3.4 SF 425 Compatibility Tags for Built Distributions Daniel Holth 3.4 SF 427 The Wheel Binary Package Format 1.0 Daniel Holth SF 428 The pathlib module – object-oriented filesystem paths Antoine Pitrou 3.4 SF 435 Adding an Enum type to the Python standard library Barry Warsaw, Eli Bendersky, Ethan Furman 3.4 SF 436 The Argument Clinic DSL Larry Hastings 3.4 SF 440 Version Identification and Dependency Specification Alyssa Coghlan, Donald Stufft SF 441 Improving Python ZIP Application Support Daniel Holth, Paul Moore 3.5 SF 442 Safe object finalization Antoine Pitrou 3.4 SF 443 Single-dispatch generic functions Łukasz Langa 3.4 SF 445 Add new APIs to customize Python memory allocators Victor Stinner 3.4 SF 446 Make newly created file descriptors non-inheritable Victor Stinner 3.4 SF 448 Additional Unpacking Generalizations Joshua Landau 3.5 SF 450 Adding A Statistics Module To The Standard Library Steven D’Aprano 3.4 SF 451 A ModuleSpec Type for the Import System Eric Snow 3.4 SF 453 Explicit bootstrapping of pip in Python installations Donald Stufft, Alyssa Coghlan SF 454 Add a new tracemalloc module to trace Python memory allocations Victor Stinner 3.4 SF 456 Secure and interchangeable hash algorithm Christian Heimes 3.4 SF 461 Adding % formatting to bytes and bytearray Ethan Furman 3.5 SF 465 A dedicated infix operator for matrix multiplication Nathaniel J. Smith 3.5 SF 466 Network Security Enhancements for Python 2.7.x Alyssa Coghlan 2.7.9 SF 468 Preserving the order of **kwargs in a function. Eric Snow 3.6 SF 471 os.scandir() function – a better and faster directory iterator Ben Hoyt 3.5 SF 475 Retry system calls failing with EINTR Charles-François Natali, Victor Stinner 3.5 SF 476 Enabling certificate verification by default for stdlib http clients Alex Gaynor 2.7.9, 3.4.3, 3.5 SF 477 Backport ensurepip (PEP 453) to Python 2.7 Donald Stufft, Alyssa Coghlan SF 479 Change StopIteration handling inside generators Chris Angelico, Guido van Rossum 3.5 SF 484 Type Hints Guido van Rossum, Jukka Lehtosalo, Łukasz Langa 3.5 SF 485 A Function for testing approximate equality Christopher Barker 3.5 SF 486 Make the Python Launcher aware of virtual environments Paul Moore 3.5 SF 487 Simpler customisation of class creation Martin Teichmann 3.6 SF 488 Elimination of PYO files Brett Cannon 3.5 SF 489 Multi-phase extension module initialization Petr Viktorin, Stefan Behnel, Alyssa Coghlan 3.5 SF 492 Coroutines with async and await syntax Yury Selivanov 3.5 SF 493 HTTPS verification migration tools for Python 2.7 Alyssa Coghlan, Robert Kuska, Marc-André Lemburg 2.7.12 SF 495 Local Time Disambiguation Alexander Belopolsky, Tim Peters 3.6 SF 498 Literal String Interpolation Eric V. Smith 3.6 SF 503 Simple Repository API Donald Stufft SF 506 Adding A Secrets Module To The Standard Library Steven D’Aprano 3.6 SF 508 Dependency specification for Python Software Packages Robert Collins SF 515 Underscores in Numeric Literals Georg Brandl, Serhiy Storchaka 3.6 SF 517 A build-system independent format for source trees Nathaniel J. Smith, Thomas Kluyver SF 518 Specifying Minimum Build System Requirements for Python Projects Brett Cannon, Nathaniel J. Smith, Donald Stufft SF 519 Adding a file system path protocol Brett Cannon, Koos Zevenhoven 3.6 SF 520 Preserving Class Attribute Definition Order Eric Snow 3.6 SF 523 Adding a frame evaluation API to CPython Brett Cannon, Dino Viehland 3.6 SF 524 Make os.urandom() blocking on Linux Victor Stinner 3.6 SF 525 Asynchronous Generators Yury Selivanov 3.6 SF 526 Syntax for Variable Annotations Ryan Gonzalez, Philip House, Ivan Levkivskyi, Lisa Roach, Guido van Rossum 3.6 SF 527 Removing Un(der)used file types/extensions on PyPI Donald Stufft SF 528 Change Windows console encoding to UTF-8 Steve Dower 3.6 SF 529 Change Windows filesystem encoding to UTF-8 Steve Dower 3.6 SF 530 Asynchronous Comprehensions Yury Selivanov 3.6 SF 538 Coercing the legacy C locale to a UTF-8 based locale Alyssa Coghlan 3.7 SF 539 A New C-API for Thread-Local Storage in CPython Erik M. Bray, Masayuki Yamamoto 3.7 SF 540 Add a new UTF-8 Mode Victor Stinner 3.7 SF 544 Protocols: Structural subtyping (static duck typing) Ivan Levkivskyi, Jukka Lehtosalo, Łukasz Langa 3.8 SF 552 Deterministic pycs Benjamin Peterson 3.7 SF 553 Built-in breakpoint() Barry Warsaw 3.7 SF 557 Data Classes Eric V. Smith 3.7 SF 560 Core support for typing module and generic types Ivan Levkivskyi 3.7 SF 561 Distributing and Packaging Type Information Emma Harper Smith 3.7 SF 562 Module __getattr__ and __dir__ Ivan Levkivskyi 3.7 SF 564 Add new time functions with nanosecond resolution Victor Stinner 3.7 SF 565 Show DeprecationWarning in __main__ Alyssa Coghlan 3.7 SF 566 Metadata for Python Software Packages 2.1 Dustin Ingram 3.x SF 567 Context Variables Yury Selivanov 3.7 SF 570 Python Positional-Only Parameters Larry Hastings, Pablo Galindo Salgado, Mario Corchero, Eric N. Vander Weele 3.8 SF 572 Assignment Expressions Chris Angelico, Tim Peters, Guido van Rossum 3.8 SF 573 Module State Access from C Extension Methods Petr Viktorin, Alyssa Coghlan, Eric Snow, Marcel Plch 3.9 SF 574 Pickle protocol 5 with out-of-band data Antoine Pitrou 3.8 SF 578 Python Runtime Audit Hooks Steve Dower 3.8 SF 584 Add Union Operators To dict Steven D’Aprano, Brandt Bucher 3.9 SF 585 Type Hinting Generics In Standard Collections Łukasz Langa 3.9 SF 586 Literal Types Michael Lee, Ivan Levkivskyi, Jukka Lehtosalo 3.8 SF 587 Python Initialization Configuration Victor Stinner, Alyssa Coghlan 3.8 SF 589 TypedDict: Type Hints for Dictionaries with a Fixed Set of Keys Jukka Lehtosalo 3.8 SF 590 Vectorcall: a fast calling protocol for CPython Mark Shannon, Jeroen Demeyer 3.8 SF 591 Adding a final qualifier to typing Michael J. Sullivan, Ivan Levkivskyi 3.8 SF 592 Adding “Yank” Support to the Simple API Donald Stufft SF 593 Flexible function and variable annotations Till Varoquaux, Konstantin Kashin 3.9 SF 594 Removing dead batteries from the standard library Christian Heimes, Brett Cannon 3.11 SF 597 Add optional EncodingWarning Inada Naoki 3.10 SF 600 Future ‘manylinux’ Platform Tags for Portable Linux Built Distributions Nathaniel J. Smith, Thomas Kluyver SF 604 Allow writing union types as X | Y Philippe PRADOS, Maggie Moss 3.10 SF 610 Recording the Direct URL Origin of installed distributions Stéphane Bidoul, Chris Jerdonek SF 612 Parameter Specification Variables Mark Mendoza 3.10 SF 613 Explicit Type Aliases Shannon Zhu 3.10 SF 614 Relaxing Grammar Restrictions On Decorators Brandt Bucher 3.9 SF 615 Support for the IANA Time Zone Database in the Standard Library Paul Ganssle 3.9 SF 616 String methods to remove prefixes and suffixes Dennis Sweeney 3.9 SF 617 New PEG parser for CPython Guido van Rossum, Pablo Galindo Salgado, Lysandros Nikolaou 3.9 SF 618 Add Optional Length-Checking To zip Brandt Bucher 3.10 SF 621 Storing project metadata in pyproject.toml Brett Cannon, Dustin Ingram, Paul Ganssle, Pradyun Gedam, Sébastien Eustace, Thomas Kluyver, Tzu-ping Chung SF 623 Remove wstr from Unicode Inada Naoki 3.10 SF 624 Remove Py_UNICODE encoder APIs Inada Naoki 3.11 SF 625 Filename of a Source Distribution Tzu-ping Chung, Paul Moore SF 626 Precise line numbers for debugging and other tools. Mark Shannon 3.10 SF 627 Recording installed projects Petr Viktorin SF 628 Add math.tau Alyssa Coghlan 3.6 SF 629 Versioning PyPI’s Simple API Donald Stufft SF 632 Deprecate distutils module Steve Dower 3.10 SF 634 Structural Pattern Matching: Specification Brandt Bucher, Guido van Rossum 3.10 SF 639 Improving License Clarity with Better Package Metadata Philippe Ombredanne, C.A.M. Gerlach, Karolina Surma SF 643 Metadata for Package Source Distributions Paul Moore SF 644 Require OpenSSL 1.1.1 or newer Christian Heimes 3.10 SF 646 Variadic Generics Mark Mendoza, Matthew Rahtz, Pradeep Kumar Srinivasan, Vincent Siles 3.11 SF 647 User-Defined Type Guards Eric Traut 3.10 SF 649 Deferred Evaluation Of Annotations Using Descriptors Larry Hastings 3.14 SF 652 Maintaining the Stable ABI Petr Viktorin 3.10 SF 654 Exception Groups and except* Irit Katriel, Yury Selivanov, Guido van Rossum 3.11 SF 655 Marking individual TypedDict items as required or potentially-missing David Foster 3.11 SF 656 Platform Tag for Linux Distributions Using Musl Tzu-ping Chung SF 657 Include Fine Grained Error Locations in Tracebacks Pablo Galindo Salgado, Batuhan Taskaya, Ammar Askar 3.11 SF 660 Editable installs for pyproject.toml based builds (wheel based) Daniel Holth, Stéphane Bidoul SF 667 Consistent views of namespaces Mark Shannon, Tian Gao 3.13 SF 669 Low Impact Monitoring for CPython Mark Shannon 3.12 SF 670 Convert macros to functions in the Python C API Erlend Egeberg Aasland, Victor Stinner 3.11 SF 673 Self Type Pradeep Kumar Srinivasan, James Hilton-Balfe 3.11 SF 675 Arbitrary Literal String Type Pradeep Kumar Srinivasan, Graham Bleaney 3.11 SF 678 Enriching Exceptions with Notes Zac Hatfield-Dodds 3.11 SF 680 tomllib: Support for Parsing TOML in the Standard Library Taneli Hukkinen, Shantanu Jain 3.11 SF 681 Data Class Transforms Erik De Bonte, Eric Traut 3.11 SF 682 Format Specifier for Signed Zero John Belmonte 3.11 SF 683 Immortal Objects, Using a Fixed Refcount Eric Snow, Eddie Elizondo 3.12 SF 684 A Per-Interpreter GIL Eric Snow 3.12 SF 685 Comparison of extra names for optional distribution dependencies Brett Cannon SF 688 Making the buffer protocol accessible in Python Jelle Zijlstra 3.12 SF 689 Unstable C API tier Petr Viktorin 3.12 SF 692 Using TypedDict for more precise **kwargs typing Franek Magiera 3.12 SF 695 Type Parameter Syntax Eric Traut 3.12 SF 696 Type Defaults for Type Parameters James Hilton-Balfe 3.13 SF 697 Limited C API for Extending Opaque Types Petr Viktorin 3.12 SF 698 Override Decorator for Static Typing Steven Troxler, Joshua Xu, Shannon Zhu 3.12 SF 700 Additional Fields for the Simple API for Package Indexes Paul Moore SF 702 Marking deprecations using the type system Jelle Zijlstra 3.13 SF 705 TypedDict: Read-only items Alice Purcell 3.13 SF 706 Filter for tarfile.extractall Petr Viktorin 3.12 SF 709 Inlined comprehensions Carl Meyer 3.12 SF 715 Disabling bdist_egg distribution uploads on PyPI William Woodruff SF 721 Using tarfile.data_filter for source distribution extraction Petr Viktorin 3.12 SF 723 Inline script metadata Ofek Lev SF 730 Adding iOS as a supported platform Russell Keith-Magee 3.13 SF 734 Multiple Interpreters in the Stdlib Eric Snow 3.14 SF 735 Dependency Groups in pyproject.toml Stephen Rosen SF 737 C API to format a type fully qualified name Victor Stinner 3.13 SF 738 Adding Android as a supported platform Malcolm Smith 3.13 SF 740 Index support for digital attestations William Woodruff, Facundo Tuesca, Dustin Ingram SF 741 Python Configuration C API Victor Stinner 3.14 SF 742 Narrowing types with TypeIs Jelle Zijlstra 3.13 SF 749 Implementing PEP 649 Jelle Zijlstra 3.14 SF 750 Template Strings Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck 3.14 SF 751 A file format to record Python dependencies for installation reproducibility Brett Cannon SF 757 C API to import-export Python integers Sergey B Kirpichev, Victor Stinner 3.14 SF 758 Allow except and except* expressions without parentheses Pablo Galindo Salgado, Brett Cannon 3.14 SF 765 Disallow return/break/continue that exit a finally block Irit Katriel, Alyssa Coghlan 3.14 SF 768 Safe external debugger interface for CPython Pablo Galindo Salgado, Matt Wozniski, Ivona Stojanovic 3.14 SF 779 Criteria for supported status for free-threaded Python Thomas Wouters, Matt Page, Sam Gross 3.14 SF 782 Add PyBytesWriter C API Victor Stinner 3.15 SF 784 Adding Zstandard to the standard library Emma Harper Smith 3.14 SF 791 math.integer — submodule for integer-specific mathematics functions Neil Girdhar, Sergey B Kirpichev, Tim Peters, Serhiy Storchaka 3.15 SF 792 Project status markers in the simple index William Woodruff, Facundo Tuesca SF 3101 Advanced String Formatting Talin 3.0 SF 3102 Keyword-Only Arguments Talin 3.0 SF 3104 Access to Names in Outer Scopes Ka-Ping Yee 3.0 SF 3105 Make print a function Georg Brandl 3.0 SF 3106 Revamping dict.keys(), .values() and .items() Guido van Rossum 3.0 SF 3107 Function Annotations Collin Winter, Tony Lownds 3.0 SF 3108 Standard Library Reorganization Brett Cannon 3.0 SF 3109 Raising Exceptions in Python 3000 Collin Winter 3.0 SF 3110 Catching Exceptions in Python 3000 Collin Winter 3.0 SF 3111 Simple input built-in in Python 3000 Andre Roberge 3.0 SF 3112 Bytes literals in Python 3000 Jason Orendorff 3.0 SF 3113 Removal of Tuple Parameter Unpacking Brett Cannon 3.0 SF 3114 Renaming iterator.next() to iterator.__next__() Ka-Ping Yee 3.0 SF 3115 Metaclasses in Python 3000 Talin 3.0 SF 3116 New I/O Daniel Stutzbach, Guido van Rossum, Mike Verdone 3.0 SF 3118 Revising the buffer protocol Travis Oliphant, Carl Banks 3.0 SF 3119 Introducing Abstract Base Classes Guido van Rossum, Talin 3.0 SF 3120 Using UTF-8 as the default source encoding Martin von Löwis 3.0 SF 3121 Extension Module Initialization and Finalization Martin von Löwis 3.0 SF 3123 Making PyObject_HEAD conform to standard C Martin von Löwis 3.0 SF 3127 Integer Literal Support and Syntax Patrick Maupin 3.0 SF 3129 Class Decorators Collin Winter 3.0 SF 3131 Supporting Non-ASCII Identifiers Martin von Löwis 3.0 SF 3132 Extended Iterable Unpacking Georg Brandl 3.0 SF 3134 Exception Chaining and Embedded Tracebacks Ka-Ping Yee 3.0 SF 3135 New Super Calvin Spealman, Tim Delaney, Lie Ryan 3.0 SF 3137 Immutable Bytes and Mutable Buffer Guido van Rossum 3.0 SF 3138 String representation in Python 3000 Atsuo Ishimoto 3.0 SF 3141 A Type Hierarchy for Numbers Jeffrey Yasskin 3.0 SF 3144 IP Address Manipulation Library for the Python Standard Library Peter Moody 3.3 SF 3147 PYC Repository Directories Barry Warsaw 3.2 SF 3148 futures - execute computations asynchronously Brian Quinlan 3.2 SF 3149 ABI version tagged .so files Barry Warsaw 3.2 SF 3151 Reworking the OS and IO exception hierarchy Antoine Pitrou 3.3 SF 3154 Pickle protocol version 4 Antoine Pitrou 3.4 SF 3155 Qualified name for classes and functions Antoine Pitrou 3.3 SF 3156 Asynchronous IO Support Rebooted: the “asyncio” Module Guido van Rossum 3.3 Historical Meta-PEPs and Informational PEPs PEP Title Authors PS 5 Guidelines for Language Evolution Paul Prescod PS 6 Bug Fix Releases Aahz, Anthony Baxter IF 160 Python 1.6 Release Schedule Fred L. Drake, Jr. 1.6 IF 200 Python 2.0 Release Schedule Jeremy Hylton 2.0 IF 226 Python 2.1 Release Schedule Jeremy Hylton 2.1 IF 251 Python 2.2 Release Schedule Barry Warsaw, Guido van Rossum 2.2 IF 283 Python 2.3 Release Schedule Guido van Rossum 2.3 IF 320 Python 2.4 Release Schedule Barry Warsaw, Raymond Hettinger, Anthony Baxter 2.4 PF 347 Migrating the Python CVS to Subversion Martin von Löwis IF 356 Python 2.5 Release Schedule Neal Norwitz, Guido van Rossum, Anthony Baxter 2.5 PF 360 Externally Maintained Packages Brett Cannon IF 361 Python 2.6 and 3.0 Release Schedule Neal Norwitz, Barry Warsaw 2.6, 3.0 IF 373 Python 2.7 Release Schedule Benjamin Peterson 2.7 PF 374 Choosing a distributed VCS for the Python project Brett Cannon, Stephen J. Turnbull, Alexandre Vassalotti, Barry Warsaw, Dirkjan Ochtman IF 375 Python 3.1 Release Schedule Benjamin Peterson 3.1 PF 385 Migrating from Subversion to Mercurial Dirkjan Ochtman, Antoine Pitrou, Georg Brandl IF 392 Python 3.2 Release Schedule Georg Brandl 3.2 IF 398 Python 3.3 Release Schedule Georg Brandl 3.3 IF 404 Python 2.8 Un-release Schedule Barry Warsaw 2.8 IF 429 Python 3.4 Release Schedule Larry Hastings 3.4 PS 438 Transitioning to release-file hosting on PyPI Holger Krekel, Carl Meyer PF 449 Removal of the PyPI Mirror Auto Discovery and Naming Scheme Donald Stufft PF 464 Removal of the PyPI Mirror Authenticity API Donald Stufft PF 470 Removing External Hosting Support on PyPI Donald Stufft IF 478 Python 3.5 Release Schedule Larry Hastings 3.5 IF 494 Python 3.6 Release Schedule Ned Deily 3.6 PF 512 Migrating from hg.python.org to GitHub Brett Cannon IF 537 Python 3.7 Release Schedule Ned Deily 3.7 PF 541 Package Index Name Retention Łukasz Langa IF 569 Python 3.8 Release Schedule Łukasz Langa 3.8 PF 581 Using GitHub Issues for CPython Mariatta IF 596 Python 3.9 Release Schedule Łukasz Langa 3.9 PF 3000 Python 3000 Guido van Rossum PF 3002 Procedure for Backwards-Incompatible Changes Steven Bethard PF 3003 Python Language Moratorium Brett Cannon, Jesse Noller, Guido van Rossum PF 3099 Things that will Not Change in Python 3000 Georg Brandl PF 3100 Miscellaneous Python 3.0 Plans Brett Cannon PF 8001 Python Governance Voting Process Brett Cannon, Christian Heimes, Donald Stufft, Eric Snow, Gregory P. Smith, Łukasz Langa, Mariatta, Nathaniel J. Smith, Pablo Galindo Salgado, Raymond Hettinger, Tal Einat, Tim Peters, Zachary Ware Deferred PEPs (postponed pending further research or updates) PEP Title Authors SD 213 Attribute Access Handlers Paul Prescod 2.1 SD 219 Stackless Python Gordon McMillan 2.1 SD 222 Web Library Enhancements A.M. Kuchling 2.1 SD 233 Python Online Help Paul Prescod 2.1 SD 267 Optimized Access to Module Namespaces Jeremy Hylton 2.2 SD 269 Pgen Module for Python Jonathan Riehl 2.2 SD 280 Optimizing access to globals Guido van Rossum 2.3 SD 286 Enhanced Argument Tuples Martin von Löwis 2.3 SD 312 Simple Implicit Lambda Roman Suzi, Alex Martelli 2.4 SD 316 Programming by Contract for Python Terence Way SD 323 Copyable Iterators Alex Martelli 2.5 SD 337 Logging Usage in the Standard Library Michael P. Dubner 2.5 SD 368 Standard image protocol and class Lino Mastrodomenico 2.6, 3.0 SD 400 Deprecate codecs.StreamReader and codecs.StreamWriter Victor Stinner 3.3 SD 403 General purpose decorator clause (aka “@in” clause) Alyssa Coghlan 3.4 PD 407 New release cycle and introducing long-term support versions Antoine Pitrou, Georg Brandl, Barry Warsaw SD 419 Protecting cleanup statements from interruptions Paul Colomiets 3.3 ID 423 Naming conventions and recipes related to packaging Benoit Bryon ID 444 Python Web3 Interface Chris McDonough, Armin Ronacher SD 447 Add __getdescriptor__ method to metaclass Ronald Oussoren SD 491 The Wheel Binary Package Format 1.9 Daniel Holth SD 499 python -m foo should also bind ‘foo’ in sys.modules Cameron Simpson, Chris Angelico, Joseph Jevnik 3.10 SD 505 None-aware operators Mark E. Haase, Steve Dower 3.8 SD 532 A circuit breaking protocol and binary operators Alyssa Coghlan, Mark E. Haase 3.8 SD 533 Deterministic cleanup for iterators Nathaniel J. Smith SD 534 Improved Errors for Missing Standard Library Modules Tomáš Orsava, Petr Viktorin, Alyssa Coghlan SD 535 Rich comparison chaining Alyssa Coghlan 3.8 SD 547 Running extension modules using the -m option Marcel Plch, Petr Viktorin 3.7 SD 556 Threaded garbage collection Antoine Pitrou 3.7 SD 568 Generator-sensitivity for Context Variables Nathaniel J. Smith 3.8 SD 661 Sentinel Values Tal Einat SD 674 Disallow using macros as l-values Victor Stinner 3.12 SD 774 Removing the LLVM requirement for JIT builds Savannah Ostrowski 3.14 SD 778 Supporting Symlinks in Wheels Emma Harper Smith SD 787 Safer subprocess usage using t-strings Nick Humrich, Alyssa Coghlan 3.15 SD 3124 Overloading, Generic Functions, Interfaces, and Adaptation Phillip J. Eby SD 3143 Standard daemon process library Ben Finney 3.x SD 3150 Statement local namespaces (aka “given” clause) Alyssa Coghlan 3.4 Rejected, Superseded, and Withdrawn PEPs PEP Title Authors PW 3 Guidelines for Handling Bug Reports Jeremy Hylton PW 9 Sample Plaintext PEP Template Barry Warsaw PW 42 Feature Requests Jeremy Hylton IS 102 Doing Python Micro Releases Anthony Baxter, Barry Warsaw, Guido van Rossum IW 103 Collecting information about git Oleg Broytman SR 204 Range Literals Thomas Wouters 2.0 IW 206 Python Advanced Library A.M. Kuchling SW 209 Multi-dimensional Arrays Paul Barrett, Travis Oliphant 2.2 SR 210 Decoupling the Interpreter Loop David Ascher 2.1 SR 211 Adding A New Outer Product Operator Greg Wilson 2.1 SR 212 Loop Counter Iteration Peter Schneider-Kamp 2.1 SS 215 String Interpolation Ka-Ping Yee 2.1 IW 216 Docstring Format Moshe Zadka IR 220 Coroutines, Generators, Continuations Gordon McMillan SR 224 Attribute Docstrings Marc-André Lemburg 2.1 SR 225 Elementwise/Objectwise Operators Huaiyu Zhu, Gregory Lielens 2.1 SW 228 Reworking Python’s Numeric Model Moshe Zadka, Guido van Rossum SR 231 __findattr__() Barry Warsaw 2.1 SR 239 Adding a Rational Type to Python Christopher A. Craig, Moshe Zadka 2.2 SR 240 Adding a Rational Literal to Python Christopher A. Craig, Moshe Zadka 2.2 SS 241 Metadata for Python Software Packages A.M. Kuchling SW 242 Numeric Kinds Paul F. Dubois 2.2 SW 243 Module Repository Upload Mechanism Sean Reifschneider 2.1 SR 244 The directive statement Martin von Löwis 2.1 SR 245 Python Interface Syntax Michel Pelletier 2.2 SR 246 Object Adaptation Alex Martelli, Clark C. Evans 2.5 SR 254 Making Classes Look More Like Types Guido van Rossum 2.2 SR 256 Docstring Processing System Framework David Goodger SR 258 Docutils Design Specification David Goodger SR 259 Omit printing newline after newline Guido van Rossum 2.2 SR 262 A Database of Installed Python Packages A.M. Kuchling SR 265 Sorting Dictionaries by Value Grant Griffin 2.2 SW 266 Optimizing Global Variable/Attribute Access Skip Montanaro 2.3 SR 268 Extended HTTP functionality and WebDAV Greg Stein 2.x SR 270 uniq method for list objects Jason Petrone 2.2 SR 271 Prefixing sys.path by command line option Frédéric B. Giacometti 2.2 SR 275 Switching on Multiple Values Marc-André Lemburg 2.6 SR 276 Simple Iterator for ints Jim Althoff 2.3 SR 281 Loop Counter Iteration with range and xrange Magnus Lie Hetland 2.3 SR 284 Integer for-loops David Eppstein, Gregory Ewing 2.3 SW 288 Generators Attributes and Exceptions Raymond Hettinger 2.5 IS 291 Backward Compatibility for the Python 2 Standard Library Neal Norwitz 2.3 SR 294 Type Names in the types Module Oren Tirosh 2.5 SR 295 Interpretation of multiline string constants Stepan Koltsov 3.0 SW 296 Adding a bytes Object Type Scott Gilbert 2.3 SR 297 Support for System Upgrades Marc-André Lemburg 2.6 SW 298 The Locked Buffer Interface Thomas Heller 2.3 SR 299 Special __main__() function in modules Jeff Epler 2.3 SR 303 Extend divmod() for Multiple Divisors Thomas Bellman 2.3 SW 304 Controlling Generation of Bytecode Files Skip Montanaro IW 306 How to Change Python’s Grammar Michael Hudson, Jack Diederich, Alyssa Coghlan, Benjamin Peterson SR 310 Reliable Acquisition/Release Pairs Michael Hudson, Paul Moore 2.4 SR 313 Adding Roman Numeral Literals to Python Mike Meyer 2.4 SS 314 Metadata for Python Software Packages 1.1 A.M. Kuchling, Richard Jones 2.5 SR 315 Enhanced While Loop Raymond Hettinger, W Isaac Carroll 2.5 SR 317 Eliminate Implicit Exception Instantiation Steven Taschuk 2.4 SR 319 Python Synchronize/Asynchronize Block Michel Pelletier 2.4 SW 321 Date/Time Parsing and Formatting A.M. Kuchling 2.4 SR 325 Resource-Release Support for Generators Samuele Pedroni 2.4 SR 326 A Case for Top and Bottom Values Josiah Carlson, Terry Reedy 2.4 SR 329 Treating Builtins as Constants in the Standard Library Raymond Hettinger 2.4 SR 330 Python Bytecode Verification Michel Pelletier 2.6 SR 332 Byte vectors and String/Unicode Unification Skip Montanaro 2.5 SW 334 Simple Coroutines via SuspendIteration Clark C. Evans 3.0 SR 335 Overloadable Boolean Operators Gregory Ewing 3.3 SR 336 Make None Callable Andrew McClelland IW 339 Design of the CPython Compiler Brett Cannon SR 340 Anonymous Block Statements Guido van Rossum SS 344 Exception Chaining and Embedded Tracebacks Ka-Ping Yee 2.5 SS 345 Metadata for Python Software Packages 1.2 Richard Jones 2.7 SW 346 User Defined (“with”) Statements Alyssa Coghlan 2.5 SR 348 Exception Reorganization for Python 3.0 Brett Cannon SR 349 Allow str() to return unicode strings Neil Schemenauer 2.5 IR 350 Codetags Micah Elliott SR 351 The freeze protocol Barry Warsaw 2.5 SS 354 Enumerations in Python Ben Finney 2.6 SR 355 Path - Object oriented filesystem paths Björn Lindqvist 2.5 SW 359 The “make” Statement Steven Bethard 2.6 SR 363 Syntax For Dynamic Attribute Access Ben North SW 364 Transitioning to the Py3K Standard Library Barry Warsaw 2.6 SR 365 Adding the pkg_resources module Phillip J. Eby SS 367 New Super Calvin Spealman, Tim Delaney 2.6 SW 369 Post import hooks Christian Heimes 2.6, 3.0 SR 377 Allow __enter__() methods to skip the statement body Alyssa Coghlan 2.7, 3.1 SW 379 Adding an Assignment Expression Jervis Whitley 2.7, 3.2 SW 381 Mirroring infrastructure for PyPI Tarek Ziadé, Martin von Löwis SR 382 Namespace Packages Martin von Löwis 3.2 SS 386 Changing the version comparison module in Distutils Tarek Ziadé SR 390 Static metadata for Distutils Tarek Ziadé 2.7, 3.2 SW 395 Qualified Names for Modules Alyssa Coghlan 3.4 IW 396 Module Version Numbers Barry Warsaw PR 401 BDFL Retirement Barry Warsaw, Brett Cannon SR 402 Simplified Package Layout and Partitioning Phillip J. Eby 3.3 SW 406 Improved Encapsulation of Import State Alyssa Coghlan, Greg Slodkowicz 3.4 SR 408 Standard library __preview__ package Alyssa Coghlan, Eli Bendersky 3.3 SR 410 Use decimal.Decimal type for timestamps Victor Stinner 3.3 IS 411 Provisional packages in the Python standard library Alyssa Coghlan, Eli Bendersky 3.3 PW 413 Faster evolution of the Python Standard Library Alyssa Coghlan SR 416 Add a frozendict builtin type Victor Stinner 3.3 SW 422 Simpler customisation of class creation Alyssa Coghlan, Daniel Urban 3.5 IW 426 Metadata for Python Software Packages 2.0 Alyssa Coghlan, Daniel Holth, Donald Stufft SS 431 Time zone support improvements Lennart Regebro SW 432 Restructuring the CPython startup sequence Alyssa Coghlan, Victor Stinner, Eric Snow SS 433 Easier suppression of file descriptor inheritance Victor Stinner 3.4 SR 437 A DSL for specifying signatures, annotations and argument converters Stefan Krah 3.4 SR 439 Inclusion of implicit pip bootstrap in Python installation Richard Jones 3.4 SR 455 Adding a key-transforming dictionary to collections Antoine Pitrou 3.5 SW 459 Standard Metadata Extensions for Python Software Packages Alyssa Coghlan SW 460 Add binary interpolation and formatting Antoine Pitrou 3.5 PW 462 Core development workflow automation for CPython Alyssa Coghlan SR 463 Exception-catching expressions Chris Angelico 3.5 SW 469 Migration of dict iteration code to Python 3 Alyssa Coghlan 3.5 SR 472 Support for indexing with keyword arguments Stefano Borini, Joseph Martinot-Lagarde 3.6 SR 473 Adding structured data to built-in exceptions Sebastian Kreft PW 474 Creating forge.python.org Alyssa Coghlan PW 481 Migrate CPython to Git, Github, and Phabricator Donald Stufft SR 490 Chain exceptions at C level Victor Stinner 3.6 IR 496 Environment Markers James Polley PR 497 A standard mechanism for backward compatibility Ed Schofield SR 500 A protocol for delegating datetime methods to their tzinfo implementations Alexander Belopolsky, Tim Peters SW 501 General purpose template literal strings Alyssa Coghlan, Nick Humrich 3.12 IR 502 String Interpolation - Extended Discussion Mike G. Miller 3.6 SW 504 Using the System RNG by default Alyssa Coghlan 3.6 PR 507 Migrate CPython to Git and GitLab Barry Warsaw SS 509 Add a private version to dict Victor Stinner 3.6 SR 510 Specialize functions with guards Victor Stinner 3.6 SR 511 API for code transformers Victor Stinner 3.6 IS 513 A Platform Tag for Portable Linux Built Distributions Robert T. McGibbon, Nathaniel J. Smith SR 516 Build system abstraction for pip/conda etc Robert Collins, Nathaniel J. Smith SW 521 Managing global context via ‘with’ blocks in generators and coroutines Nathaniel J. Smith 3.6 SR 522 Allow BlockingIOError in security sensitive APIs Alyssa Coghlan, Nathaniel J. Smith 3.6 SW 531 Existence checking operators Alyssa Coghlan 3.7 SW 536 Final Grammar for Literal String Interpolation Philipp Angerer 3.7 SR 542 Dot Notation Assignment In Function Header Markus Meskanen SW 543 A Unified TLS API for Python Cory Benfield, Christian Heimes 3.7 SR 546 Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7 Victor Stinner, Cory Benfield 2.7 SR 548 More Flexible Loop Control R David Murray 3.7 SR 549 Instance Descriptors Larry Hastings 3.7 SW 550 Execution Context Yury Selivanov, Elvis Pranskevichus 3.7 IW 551 Security transparency in the Python runtime Steve Dower 3.7 SS 554 Multiple Interpreters in the Stdlib Eric Snow 3.13 SW 555 Context-local variables (contextvars) Koos Zevenhoven 3.7 SW 558 Defined semantics for locals() Alyssa Coghlan 3.13 SR 559 Built-in noop() Barry Warsaw 3.7 SS 563 Postponed Evaluation of Annotations Łukasz Langa 3.7 IS 571 The manylinux2010 Platform Tag Mark Williams, Geoffrey Thomas, Thomas Kluyver SW 575 Unifying function/method classes Jeroen Demeyer 3.8 SW 576 Rationalize Built-in function classes Mark Shannon 3.8 SW 577 Augmented Assignment Expressions Alyssa Coghlan 3.8 SR 580 The C call protocol Jeroen Demeyer 3.8 SR 582 Python local packages directory Kushal Das, Steve Dower, Donald Stufft, Alyssa Coghlan 3.12 IW 583 A Concurrency Memory Model for Python Jeffrey Yasskin IW 595 Improving bugs.python.org Ezio Melotti, Berker Peksag IW 598 Introducing incremental feature releases Alyssa Coghlan 3.9 IS 599 The manylinux2014 Platform Tag Dustin Ingram SR 601 Forbid return/break/continue breaking out of finally Damien George, Batuhan Taskaya 3.8 IR 605 A rolling feature release stream for CPython Steve Dower, Alyssa Coghlan 3.9 SR 606 Python Compatibility Version Victor Stinner 3.9 SR 608 Coordinated Python release Miro Hrončok, Victor Stinner 3.9 SW 611 The one million limit Mark Shannon SW 620 Hide implementation details from the C API Victor Stinner 3.12 SS 622 Structural Pattern Matching Brandt Bucher, Daniel F Moisset, Tobias Kohn, Ivan Levkivskyi, Guido van Rossum, Talin 3.10 SS 631 Dependency specification in pyproject.toml based on PEP 508 Ofek Lev SR 633 Dependency specification in pyproject.toml using an exploded TOML table Laurie Opperman, Arun Babu Neelicattu SR 637 Support for indexing with keyword arguments Stefano Borini 3.10 SR 640 Unused variable syntax Thomas Wouters 3.10 SR 641 Using an underscore in the version portion of Python 3.10 compatibility tags Brett Cannon, Steve Dower, Barry Warsaw 3.10 SR 642 Explicit Pattern Syntax for Structural Pattern Matching Alyssa Coghlan 3.10 SW 645 Allow writing optional types as x? Maggie Moss SR 648 Extensible customizations of the interpreter at startup Mario Corchero 3.11 SW 650 Specifying Installer Requirements for Python Projects Vikram Jayanthi, Dustin Ingram, Brett Cannon SR 651 Robust Stack Overflow Handling Mark Shannon SR 662 Editable installs via virtual wheels Bernát Gábor IR 663 Standardizing Enum str(), repr(), and format() behaviors Ethan Furman 3.11 SR 665 A file format to list Python dependencies for reproducibility of an application Brett Cannon, Pradyun Gedam, Tzu-ping Chung SR 666 Reject Foolish Indentation Laura Creighton 2.2 SR 677 Callable Type Syntax Steven Troxler, Pradeep Kumar Srinivasan 3.11 SR 679 New assert statement syntax with parentheses Pablo Galindo Salgado, Stan Ulbrych 3.15 SR 690 Lazy Imports Germán Méndez Bravo, Carl Meyer 3.12 SW 704 Require virtual environments by default for package installers Pradyun Gedam SR 707 A simplified signature for __exit__ and __aexit__ Irit Katriel 3.12 SR 712 Adding a “converter” parameter to dataclasses.field Joshua Cannon 3.13 SR 713 Callable Modules Amethyst Reese 3.12 SR 722 Dependency specification for single-file scripts Paul Moore SW 724 Stricter Type Guards Rich Chiodo, Eric Traut, Erik De Bonte 3.13 SR 726 Module __setattr__ and __delattr__ Sergey B Kirpichev 3.13 SW 727 Documentation in Annotated Metadata Sebastián Ramírez 3.13 SR 736 Shorthand syntax for keyword arguments at invocation Joshua Bambrick, Chris Angelico 3.14 SR 754 IEEE 754 Floating Point Special Values Gregory R. Warnes 2.3 SW 756 Add PyUnicode_Export() and PyUnicode_Import() C functions Victor Stinner 3.14 SW 759 External Wheel Hosting Barry Warsaw, Emma Harper Smith SW 760 No More Bare Excepts Pablo Galindo Salgado, Brett | 2026-01-13T08:49:04 |
https://www.trustpilot.com/review/ruul.io | Ruul Reviews | Read Customer Service Reviews of ruul.io Suggested companies Paddle paddle.com • 10K reviews 4.1 Payhip - Sell Digital Products payhip.com • 361 reviews 4.4 Xolo www.xolo.io • 421 reviews 3.8 Categories Blog Log in For businesses For businesses Log in Categories Blog Money & Insurance Investments & Wealth Alternative Financial Service Ruul Summary About Reviews Visit website Write a review Visit website Claimed profile Ruul Reviews 431 • 4.5 Alternative Financial Service Write a review Visit website Write a review Companies on Trustpilot aren't allowed to offer incentives or pay to hide reviews. Review summary Based on reviews, created with AI Reviewers overwhelmingly had a great experience with this company. Customers consistently praise the platform's user-friendliness and efficiency, noting how it simplifies invoicing and payment management. People appreciate the responsiveness and professionalism of the support team, highlighting thei r ability to resolve issues quickly and provide helpful assistance. The fast payment processing and the overall ease of use of the system are also frequently mentioned as positive aspects. Consumers value the prompt and solution-oriented approach of the staff, with many expressing gratitude for the personalized support they received. The platform is considered a great tool for freelancers, making it easier to manage finances and receive payments from international clients. While opinions on payment processes are mixed, the positive feedback on customer service, user experience, and response times suggests a high level of satisfaction overall. See more Based on these reviews Furkan Yıldız Dec 13, 2025 I am a freelance network administrator and software developer. I encountered Ruul when a company I worked with required invoicing. It was an excellent experience. In fact, there was an issue because... See more Company replied Beytullah Gümüş Nov 20, 2025 My Experience with Ruul Payment System (8 Months) I have been using the Ruul payment system for 8 months now for my freelance graphic design work, and I am completely satisfied with the ser... See more Company replied Eren T. Sep 15, 2025 Ruul.io made my entire process smooth and stress-free. Their platform is super easy to use and very reliable — exactly what I needed. Special thanks to Onur for the amazing support, he went above and... See more Company replied ZB Zoe Barnett Mar 3, 2025 Verified No problems with payment. Invoicing works well and payments come through promptly. It feels a bit basic. I'd like to be able to save standard invoice items to reuse in future invoices, and there's... See more Company replied Ummet Kucuker Oct 21, 2025 I am working internationally, for other countries around the world. Getting my payments fast. They respond very fast and kindly to all my questions. Love this! Thé solution for freelancers to get paym... See more Company replied UÇ Utku Ç Jul 23, 2025 Ruul was suggested to me by a friend of mine who is also working as a freelancer and contractor. Altough I am not a person who quickly trust trying someting new, with its simple pages and fast respons... See more Company replied Oliviu-Alexandru Rogozan Oct 31, 2025 Ruul.io has been a complete game changer in how I handle client payments and invoices. It is the perfect transition tool between being independent and a professional entity - there... See more Company replied Murat Tahsin Ceran Oct 9, 2025 Ruul has added a new dimension to my life. I have been working with Ruul for about three years now and I am very satisfied with them. Their quick responses and solution-oriented approach are incredibl... See more Company replied Kaya Jun 17, 2025 When I reached out for help, I couldn’t believe how quickly the issue was resolved. If I had been working with another company, it probably would have taken days but they managed to sort it out in jus... See more Company replied İdil Turan Oct 17, 2025 Their quick response and solution-oriented approach helped me resolve my issue in a short time. Thank you for your attention and support. Company replied Hande Akmehmetoğlu Sep 2, 2025 I've been working with Ruul team for sometime and when I have a question they replied me back quickly and solved my problem without hesitation. I feel very safe and connected with them. Thank you so m... See more Company replied Asım Hocagil Jul 9, 2025 Excellent Support – Thank You, Onur! Ruul’s customer representative Onur was extremely helpful, patient, and solution-oriented throughout the entire process. He listened carefully to all my questio... See more Company replied Buse Ertarman Apr 28, 2025 best application for freelancers ever-made. it's kind of hard to tell how it's working to old school accountants but faq sections and communication desk is always ready to help! Company replied erdem ugur Oct 3, 2025 Working with the Ruul team is always a pleasure. Their ability to provide solutions on the spot is very important to me. Thanks to the entire Ruul team. Company replied NA nadir a Jan 15, 2025 It works quite successfully. Fast support and getting paid without delay is a pleasure. Thank you to everyone for their efforts. Company replied ES Earvin Sosa Jul 29, 2025 Onur was really helpful, actually all of them are amazing including my previous rep Cansu. Overall satisfied with the services they provide. Company replied Cesar Serrano May 28, 2025 customer service is the best no bots, no ia, a real perosn is what need to make things easier and faster!! Company replied ÇÜ Çağdaş Ünal Jun 3, 2025 Verified Ruul makes invoicing simple and stress-free. The whole process is clear and easy to follow. If I ever have a question, the team is quick to help and always friendly. Getting paid on time is a big plus... See more Company replied VA VasylKostyniuk May 14, 2025 Ruul is always doing a great work for me. And their supports are very helpful to understand the status. Company replied Hülya Ayaz Aug 29, 2025 Ayça Hanım from the Turkish team helped me a lot during a payment issue. She was kind and very helpful. Thank you Company replied Kateryna RIMIKHANOVA Aug 17, 2025 Love everything about it! Really easy to use and if u don't understand something, the support team replies fast Company replied sensoy Sep 1, 2025 I use it for the invoicing with my work. Works smoothly and customer support is really fast and helpful. Company replied Ozgun Gobel Sep 19, 2025 Verified Even though it was my first time using it, it was fast and solution-oriented. It quickly solved exactly what I needed! Company replied Hamraoui Hiba Jul 28, 2025 Freelance can be a great first job really. It makes me able to fix my own working hours and work from anywhere freely Company replied Oluwatomiwa Adebisi Oct 13, 2025 They're very transparent, the customer service is excellent, and the payouts are quick for invoices Company replied ZS Zoe Saglam Aug 26, 2025 Fast support turnaround and helpful team. Thank you. Company replied DS Deepak Sanan Feb 22, 2025 Verified Extremely simplified sign up process, fast payment. I experienced no frustration, only smiles !!! Company replied kore kuge Jul 25, 2025 The response was very quick and accurate. Thank you! Company replied GB GAYE BERNA Jun 2, 2025 Customer service was so great and fast. Company replied Vladislav Rybak Sep 25, 2025 No problem with transaction. Best support. Company replied FR FrogWizard69 Apr 16, 2025 Great system, great work, amazing team Company replied Arda Batuhan Demir Apr 9, 2025 Great system, great work, amazing team Company replied VM Valentin M Mar 5, 2025 Verified Great service. Company replied FD Fayssal Djam-mal Mar 14, 2025 Verified Good support Company replied DE Derya Sep 10, 2025 Tank you very much onur bey🙏🙏 Company replied Dustin Wiens Updated Sep 20, 2025 took payment. never gave it to the company. now me and the company are out. do not recommend Updated - money returned, still dont recommend Company replied Muhammad Ali Nasir UD Din Aug 1, 2025 It is quite good platform , costumer service is impressive and faster. If this platform gives clients to search option for getting best talents available on their platform, with their low commission... See more Company replied Renato Updated Sep 30, 2025 Unfortunately they change compliance (without prior notice to prevent issues at payments receivings) and service cannot be used if you are from Venezuela citizen or Venezuela Resident, so we can not... See more Company replied See all 431 reviews We perform checks on reviews Company details Active Trustpilot subscription Alternative Financial Service Written by the company Invoicing and payment collection for freelancers. No company needed. Just Ruul. Contact info Hjälmaregatan 3, 201 23, Malmö, Sweden info@ruul.io ruul.io 4.5 Excellent 431 reviews 5-star 4-star 3-star 2-star 1-star How is the TrustScore calculated? Replied to 100% of negative reviews Typically replies within 24 hours How this company uses Trustpilot People also looked at Paddle paddle.com 4.1 (10K) Payhip - Sell Digital Products payhip.com 4.4 (361) Xolo www.xolo.io 3.8 (421) Lemon Squeezy lemonsqueezy.com 1.3 (104) Dodo Payments dodopayments.com 3.4 (55) Paidwork paidwork.com 4.4 (47K) Whop whop.com 3.8 (2K) Enty enty.io 3.8 (67) 4.5 All reviews 431 total ● Write a review 5-star 89% 4-star 4% 3-star 1% 2-star 1% 1-star 5% How Trustpilot labels reviews More filters Most recent Merged reviews and profile Read more This profile was merged with one or more other Trustpilot profiles belonging to this company. Some reviews shown here were originally from another profile, but now appear in one place. Profiles can be merged for reasons such as identical domains, rebranding, or change in ownership. Read more Furkan Yıldız TR • 1 review Dec 13, 2025 I am a freelance network administrator… I am a freelance network administrator and software developer. I encountered Ruul when a company I worked with required invoicing. It was an excellent experience. In fact, there was an issue because I had incorrectly described the service I provided. After I explained the details, they understood and completed the process in just half a day. The payment was transferred to me exactly when Mr. Onur Karagöz said it would be, which renewed my trust in them. I highly recommend them to everyone. December 12, 2025 Unprompted review Reply from Ruul Dec 15, 2025 Thank you for sharing your experience. We’re glad to hear that the issue was clarified quickly and the process was completed smoothly. It’s great to know everything was resolved as explained and that your payment was delivered on time. We appreciate your trust and recommendation. 💙 Beytullah Gümüş TR • 1 review Nov 20, 2025 My Experience with Ruul Payment System (8 Months) My Experience with Ruul Payment System (8 Months) I have been using the Ruul payment system for 8 months now for my freelance graphic design work, and I am completely satisfied with the service. I highly recommend it! Here are the features that stand out: Automated Invoicing: The system automatically generates and sends invoices to my clients every month, which is a huge time-saver. Prompt Payments: The paid invoices are transferred to my account flawlessly within just 2 business days. This reliability is crucial for my cash flow. Exceptional Customer Service: The customer service team is understanding, kind, and incredibly helpful. In short, I am extremely happy with Ruul and wholeheartedly recommend it to fellow freelancers! May 15, 2025 Unprompted review Reply from Ruul Nov 20, 2025 Dear Beytullah, Thank you for taking the time to write such a detailed review and your kind words. We are delighted to hear about your satisfaction with our services, and we will do our best to maintain this level of satisfaction going forward. Your trust and support are invaluable to us, and we are here for you every step of the way. AB Alessandro Beggi IT • 1 review Nov 11, 2025 Account closed, customers reimbursed, and money lost The first withdrawal went through successfully, the second withdrawal was blocked, customers were refunded, and I lost my money working for free. There couldn't be a worse company. What's more, they don't warn you if there's a problem. I had to contact customer service to get information about my withdrawal and found out that my account had been closed and all customers reimbursed. There are better companies out there. November 11, 2025 Unprompted review Reply from Ruul Updated Nov 12, 2025 Hello Alessandro, We understand your frustration and regret that this situation caused inconvenience. To meet financial and regulatory obligations, we conduct regular risk and compliance reviews across all transactions. Following one of these standard reviews, your account was closed due to specific risk indicators identified during the process. All related buyers were fully reimbursed to ensure fairness and transparency. For privacy and data protection reasons, we’re unable to share further details here. However, our team has already provided you with the relevant information via email. If you have any additional questions, please feel free to reply to that message, and we’ll be glad to assist further. Oliviu-Alexandru Rogozan RO • 2 reviews Oct 31, 2025 The Most Reliable Platform for Global Freelance Payments Ruul.io has been a complete game changer in how I handle client payments and invoices. It is the perfect transition tool between being independent and a professional entity - there is no need for a company to be established, yet I can send compliant invoices and receive payments from anywhere in the world very quickly. One of the main things that really emphasized is the platform safety and transparency. Money transfers happen at the exact time as they are announced, fees are reasonable and the support team members really give you the correct answers instead of just sending you the pre-made templates. The user interface is very neat, easy to understand and it can deal with different currencies without any problem. If you are a freelancer, a consultant or a digital nomad and thus, you work with international clients, then Ruul.io should not be looked at only as a tool that makes your work easier, rather it is an indispensable one. Very few are the services that save you so much time and at the same time give you total peace of mind. October 31, 2025 Unprompted review Reply from Ruul Oct 31, 2025 Thank you so much for this thoughtful and detailed review! We're delighted to hear that Ruul has made managing your international payments and invoicing easier and more reliable. It means a lot to know that you appreciate our transparency, support team, and platform design. We're glad to be part of your professional journey!💙 Ummet Kucuker TR • 1 review Oct 21, 2025 Thé solution for freelancers to get payments easily! I am working internationally, for other countries around the world. Getting my payments fast. They respond very fast and kindly to all my questions. Love this! Thé solution for freelancers to get payments easily! October 21, 2025 Unprompted review Reply from Ruul Oct 21, 2025 Thank you so much for your kind words. We’re happy to hear that you’re enjoying the fast payouts and quick support. We’re always here to help!💙 Sar Solut MU • 1 review Updated Oct 20, 2025 Ruul Space UPDATE 2 STAR: Thank you for reaching out personally via email. I will wait and will upgrade to 5 STAR after you bring the new features in the specified timeline. ________________________________ ORIGINAL REVIEW 1 STAR: It is sad to say that Ruul is not taking users feedbacks and suggestions into consideration. Additionally, their customer agent named Cansu is not very welcoming and not so helpful on the live chat: 1) It has been already 4 months since I contacted them to request the implementation of Euro and Pound Sterling to the Ruul Space as they have only USD. Then, just to give an answer, they just replied that they are already working on it but until now absolutely nothing. 2) As already mentioned, they impose only USD in the Ruul Space, but then, It is unbelievable how you can't sell a product for more than $1000. They put a crazy limit of $1000 on products price in the Ruul Space. 3) You can't withdraw from the Ruul Space to Binance, and once again absolutely nothing is changing since the beginning. ~ All these important things are not improving even though they change the Ruul Space design and layout etc every week. This means that they are just focusing on improving the interface appearance, but not actually on improving the important features related to the products creation process which is the most essential. I will continue to wait for a little bit more before shifting to another payment service provider if nothing more happens. July 1, 2025 Unprompted review Reply from Ruul Oct 20, 2025 Dear Jean Stephane, Thank you for sharing your feedback with us. We’ve contacted you directly to provide updates on your product-related suggestions. Since your last interaction with us about two months ago, several of the improvements you mentioned have already been implemented or are now in the final stages of development. Our team has shared the latest status with you by email. Please note that certain product removals or verification cases are managed strictly by our compliance department, which may occasionally limit the level of detail our support team can provide in real-time. We appreciate your understanding in this regard. We truly value your experience and appreciate your input. It helps us make Ruul better for everyone. İdil Turan GB • 2 reviews Oct 17, 2025 Their quick response and… Their quick response and solution-oriented approach helped me resolve my issue in a short time. Thank you for your attention and support. October 17, 2025 Unprompted review Reply from Ruul Oct 17, 2025 Dear Idil, We are delighted to hear that you are satisfied with our services! Thank you for your cooperation and your support. Keep Ruuling 💙 Ilyas Kerbal MA • 5 reviews Oct 17, 2025 Verification process will ruin your business I’ve used this platform multiple times to receive payments from companies, but I will no longer be using it. Their compliance process is poorly managed and can seriously disrupt your income. The team takes several hours ; sometimes even entire weekends ; to verify whether a payment is eligible, and in the meantime, funds are refunded to clients almost instantly without proper verification. Because of this, I lost a small contract with an Indian company that received my completed work and got their payment refunded within 24 hours ; leaving me unpaid. I strongly advise others to consider alternative platforms that verify transactions before releasing or refunding funds. October 9, 2025 Unprompted review Reply from Ruul Oct 17, 2025 Dear Elyas, We’re sorry to hear about your frustration regarding this case. To provide clarity, the transaction was paused due to the absence of crucial documentation required under our compliance and verification framework. The documents submitted for KYB verification could not be validated, as they were not obtained from official authorities. As a result, the payment could not be processed. In line with our policies, the client’s funds were immediately refunded to their original payment method, ensuring full transparency and security for both parties. Ruul operates under strict financial and regulatory standards. While these procedures may sometimes cause delays, they are essential to protecting our users, preventing misuse, and maintaining the integrity of our platform. Oluwatomiwa Adebisi NG • 1 review Oct 13, 2025 Nice Service They're very transparent, the customer service is excellent, and the payouts are quick for invoices October 13, 2025 Unprompted review Reply from Ruul Oct 14, 2025 Thank you for your kind words! We're happy to hear that you’re satisfied with our transparency, support, and quick payouts. Your trust means a lot to us! 💙 Murat Tahsin Ceran TR • 1 review Oct 9, 2025 Ruul has added a new dimension to my… Ruul has added a new dimension to my life. I have been working with Ruul for about three years now and I am very satisfied with them. Their quick responses and solution-oriented approach are incredibly good. They can provide you with instant support in any language, which is a huge advantage for me. I am so glad I found you, Ruul. I am very happy to have you in my life. October 9, 2025 Unprompted review Reply from Ruul Oct 9, 2025 Thank you for your wonderful words! We’re so happy to hear that Ruul has made such a positive impact and that our team’s quick, solution-oriented support has been helpful to you. We’re grateful to have you with us! 💙 erdem ugur TR • 1 review Oct 3, 2025 Working with the Ruul team is always a… Working with the Ruul team is always a pleasure. Their ability to provide solutions on the spot is very important to me. Thanks to the entire Ruul team. October 3, 2025 Unprompted review Reply from Ruul Oct 3, 2025 Thank you for your kind words! We’re glad our team’s quick solutions have made a difference for you. We truly appreciate your trust and support. 💙 MA Mark EE • 1 review Sep 25, 2025 Terrible Terrible. They block client payments without any explanation or apology. After working with them over a year, they out of nowhere told me that they no longer accept payments from a client, AFTER THE CLIENT HAD ALREADY PAID. Client was a big company in Europe, not some random shady company. I sent the invoice 3 weeks before the payment and they could have told me the info then, but nope. They said after the payment that we dont accept it and we have to send it back. This caused a huge problem which took nearly a month to solve. Do not trust this company, they dont care about you and I never intend to work with them again. No apology, no explanation, no nothing from their side. September 3, 2025 Unprompted review Reply from Ruul Sep 26, 2025 Dear Mark, Thank you for sharing your feedback. We sincerely apologize for the frustration this situation has caused you. We recently implemented stricter controls as part of our compliance framework to ensure all transactions remain compliant with regulatory standards. Unfortunately, during this transition, your case was affected. While your payments were refunded, we acknowledge the disappointment caused by the delay and apologize once again for the inconvenience. At Ruul, maintaining compliance and secure operations is crucial to protecting both our users and their clients. Although such changes may cause temporary frustration, they are ultimately in place to safeguard the integrity of our entire platform. Thank you for your understanding. Vladislav Rybak UA • 1 review Sep 25, 2025 Best support No problem with transaction. Best support. September 25, 2025 Unprompted review Reply from Ruul Sep 25, 2025 Thank you for your feedback! We’re happy to hear everything went smoothly and that our team could support you. 💙 Ozgun Gobel TR • 2 reviews Sep 19, 2025 Verified Even though it was my first time using… Even though it was my first time using it, it was fast and solution-oriented. It quickly solved exactly what I needed! March 28, 2025 Reply from Ruul Sep 22, 2025 Thank you for sharing your experience! We’re glad to hear your first time using Ruul went smoothly and that everything was resolved quickly.💙 Dustin Wiens CA • 1 review Updated Sep 20, 2025 bad experience took payment. never gave it to the company. now me and the company are out. do not recommend Updated - money returned, still dont recommend September 15, 2025 Unprompted review Reply from Ruul Sep 17, 2025 Dear Dustin, Thank you for sharing your feedback. We want to clarify the status for you and for others reading: - The service you purchased was canceled because it did not comply with our Acceptable Use Policy, and your seller was informed accordingly. - The refund was initially unsuccessful due to a technical issue, but it was re-initiated and confirmed by our finance team. Proof of refund has been shared directly with you. Since 2017, Ruul has been supporting users worldwide with secure, compliant, and transparent operations. We remain committed to assisting our users fairly in all cases. For any further assistance, our support team is available Monday–Friday, CET 08:00–17:00. Eren T. TR • 2 reviews Sep 15, 2025 Stress-free, smooth. Ruul.io made my entire process smooth and stress-free. Their platform is super easy to use and very reliable — exactly what I needed. Special thanks to Onur for the amazing support, he went above and beyond to help me out. Highly recommended! September 15, 2025 Unprompted review Reply from Ruul Sep 16, 2025 Thank you for the fantastic feedback! We’re delighted to hear the platform has been easy and reliable for you, and that our team could provide the support you needed. Your recommendation means a lot. 💙 Emad Mayati TR • 2 reviews Sep 13, 2025 Payment Stuck, Transaction Marked as Canceled, No Support Response one of the transactions was initiated, but its status later changed to Canceled. The amount is still pending in my account, and there are no available options in the dashboard to manage or resolve this issue. I had requested a payout to my bank account, but instead of being processed, the transaction now shows as Canceled. It is unclear whether the funds will be refunded to the client or eventually transferred to me. I have already contacted customer support about this matter, but unfortunately, I received no response. The funds remain stuck, and I cannot take any action from my side. This situation is very frustrating and creates a lot of uncertainty. September 13, 2025 Unprompted review Reply from Ruul Sep 15, 2025 Dear Emad, We are glad that we resolved this matter together after our direct communication. We’d also like to clarify here for others reading: - Our team does not operate on weekends, so the case was addressed first thing Monday morning. - The payout was cancelled because the product listed did not comply with our Terms of Use. - Refunds were processed back to the buyers’ cards, and we shared the proof of refunds in full. This case has now been closed directly with the user. At Ruul, we are committed to secure, compliant, and transparent operations, and we will always take the time to resolve issues fairly with our users. Laswann Brownfield GB • 2 reviews Updated Sep 12, 2025 Verified ONLY 1 STAR FOR NOW! ONLY 1 STAR FOR NOW! I will never understand why the platform claims that they work with 140 Different Currencies but by the end Ruul Space supports only USD. All my clients and I, we are all based in the UK and need to process all payments in £ - GBP 1 STAR for now but I WILL UPGRADE TO 5 STARS ONLY IF YOU ADD (GBP) TO THE RUUL SPACE AS SOON AS POSSIBLE! ●● UPDATE: Dear Ruul Ruul Rude! Your reply is not really sincere! Everybody should know that you flagged my initial review on the same day for containing harmful or illegal content! So, can you just tell me: Which part of my review is harmful or illegal? It is just that you don't like when your users express their thoughts and send you some suggestions to improve your service! You just want to be always in control without listening to the need of your users! Luckily, the Trustpilot Integrity Team didn't fall into your false claims and below is their reply: ((((( Hi again, We’re following up about your review of ruul.io, which was flagged for containing harmful or illegal content. Our decision We’ve assessed your review and concluded that it follows our guidelines. That's why we’ve now put your review back online.))))) BEWARE PEOPLE! IF YOU GET SOME ISSUES WITH RUUL, THEY WILL JUST FLAG YOUR BAD REVIEWS IN ORDER TO KEEP THEIR PROFILE CLEAN! BUT ANYWAY, I WILL UPGRADE THIS REVIEW TO 5 STARS AFTER YOU CHANGE YOUR BAD ATTITUDE AND IF YOU ADD £-GBP AS CURRENCY ON RUUL SPACE. BYE! September 1, 2025 Reply from Ruul Sep 5, 2025 Hi Laswann, Thank you for sharing your thoughts. Ruul offers different services, and while Payment Request supports multiple currencies, Ruul Space is a new product that currently operates in USD only. We understand this may have caused some confusion. The good news is that our team is already working on adaptive pricing for Ruul Space, which will soon make it possible to accept payments in GBP as well. We’re excited to bring this feature to our users. We truly appreciate your feedback and your interest in Ruul Space. It helps us keep improving. If you ever have any concerns, please don’t hesitate to reach out via the support box on our website. Hande Akmehmetoğlu TR • 1 review Sep 2, 2025 Ruul makes me feel safe and connected I've been working with Ruul team for sometime and when I have a question they replied me back quickly and solved my problem without hesitation. I feel very safe and connected with them. Thank you so much 🙏🏻 September 2, 2025 Unprompted review Reply from Ruul Sep 2, 2025 Thank you for your wonderful feedback! We’re so glad to hear our team’s quick support has helped you feel safe and connected. Your trust means a lot to us. 💙 sensoy TR • 1 review Sep 1, 2025 I use it for the invoicing with my… I use it for the invoicing with my work. Works smoothly and customer support is really fast and helpful. September 1, 2025 Unprompted review Reply from Ruul Updated Sep 2, 2025 Thank you for your feedback! We’re happy to hear the process has been smooth for you and that our team could support you quickly. 💙 Previous 1 2 3 4 Next page The Trustpilot Experience We're open to all Anyone can write a Trustpilot review. People who write reviews have ownership to edit or delete them at any time, and they’ll be displayed as long as an account is active . We champion verified reviews Companies can ask for reviews via automatic invitations. Labeled Verified, they’re about genuine experiences. Learn more about other kinds of reviews. We fight fake reviews We use dedicated people and clever technology to safeguard our platform. Find out how we combat fake reviews . We show the latest reviews Learn about Trustpilot’s review process . We encourage constructive feedback Here are 8 tips for writing great reviews . We verify reviewers Verification can help ensure real people are writing the reviews you read on Trustpilot. We advocate against bias Offering incentives for reviews or asking for them selectively can bias the TrustScore, which goes against our guidelines . Take a closer look are you human? Choose country United States Danmark Österreich Schweiz Deutschland Australia Canada United Kingdom Ireland New Zealand United States España Suomi Belgique België France Italia 日本 Norge Nederland Polska Brasil Portugal Sverige About About us Jobs Contact Blog How Trustpilot works Press Investor Relations Community Trust in reviews Help Center Log in Sign up Businesses Trustpilot Business Products Plans & Pricing Business Login Blog for Business Data Solutions Follow us on Legal Privacy Policy Terms & Conditions Guidelines for Reviewers System status Modern Slavery Statement © 2026 Trustpilot, Inc. All rights reserved. | 2026-01-13T08:49:04 |
https://dev.to/t/security/page/13 | Security Page 13 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Security Follow Hide Hopefully not just an afterthought! Create Post submission guidelines Write as you are pleased, be mindful and keep it civil. Older #security posts 10 11 12 13 14 15 16 17 18 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Is Your AI Agent a Compliance Risk? How to Find Violations Hidden in Traces shashank agarwal shashank agarwal shashank agarwal Follow Dec 26 '25 Is Your AI Agent a Compliance Risk? How to Find Violations Hidden in Traces # privacy # agents # security # ai Comments Add Comment 2 min read Why Post-Hoc Moderation Fails in Real-Time Systems yuer yuer yuer Follow Dec 25 '25 Why Post-Hoc Moderation Fails in Real-Time Systems # architecture # security # systemdesign Comments Add Comment 4 min read I automated data breach response - changing 50 passwords in 30 minutes instead of 8 hours The Password App The Password App The Password App Follow Dec 26 '25 I automated data breach response - changing 50 passwords in 30 minutes instead of 8 hours # security # automation # ai # productivity Comments Add Comment 3 min read Understanding AWS Network Firewall: Traffic Flow, Rules, and Logging soumi soumi soumi Follow Dec 25 '25 Understanding AWS Network Firewall: Traffic Flow, Rules, and Logging # aws # security # networkfirewall # cloudsecurity Comments Add Comment 3 min read Improved Dependency Submission for GitHub Actions Jesse Houwing Jesse Houwing Jesse Houwing Follow Dec 27 '25 Improved Dependency Submission for GitHub Actions # githubactions # github # supplychainsecurity # security Comments Add Comment 3 min read How to Improve Checkout Experiences for More Sales Priya dharshini Priya dharshini Priya dharshini Follow Dec 26 '25 How to Improve Checkout Experiences for More Sales # security # webdev # programming # ai Comments Add Comment 3 min read Decentralized Finance's Biggest Vulnerability: Why Private Key Management Can't Stay Private sid sid sid Follow Dec 25 '25 Decentralized Finance's Biggest Vulnerability: Why Private Key Management Can't Stay Private # privacy # web3 # blockchain # security 1 reaction Comments 2 comments 4 min read The $3 Billion Loss Year: End-of-Year Security Report Erick Fernandez Erick Fernandez Erick Fernandez Follow for Extropy.IO Dec 31 '25 The $3 Billion Loss Year: End-of-Year Security Report # blockchain # security # zeroknowledge # ethereum 1 reaction Comments Add Comment 4 min read Understanding Browser Automation Detection: A Technical Deep Dive for Developers Digital Growth Pro Digital Growth Pro Digital Growth Pro Follow Dec 25 '25 Understanding Browser Automation Detection: A Technical Deep Dive for Developers # javascript # security # automation # webdev Comments Add Comment 7 min read API Key Security Best Practices for 2026 Alix Alix Alix Follow Jan 9 API Key Security Best Practices for 2026 # webdev # programming # productivity # security Comments Add Comment 3 min read How Rate Limiting Saved Me $500 in One Day (Real Story) Alejandro Alejandro Alejandro Follow Dec 29 '25 How Rate Limiting Saved Me $500 in One Day (Real Story) # cloudflarechallenge # security # webdev # performance Comments Add Comment 2 min read I Let An AI Pentester: Shannon, On My Vulnerable Go App — Here’s What Happened Bhavishya Aggarwal Bhavishya Aggarwal Bhavishya Aggarwal Follow Dec 28 '25 I Let An AI Pentester: Shannon, On My Vulnerable Go App — Here’s What Happened # security # anthropicclaude # cybersecurity # softwaredevelopment Comments Add Comment 6 min read NodeJS 101 — Part 4 🔐 Authorization with JWT Akkarapon Phikulsri Akkarapon Phikulsri Akkarapon Phikulsri Follow Jan 8 NodeJS 101 — Part 4 🔐 Authorization with JWT # beginners # node # security # tutorial Comments Add Comment 4 min read I’m building a deterministic policy firewall for AI systems — looking for technical feedback Chandan Galani Chandan Galani Chandan Galani Follow Dec 25 '25 I’m building a deterministic policy firewall for AI systems — looking for technical feedback # discuss # architecture # security # ai Comments Add Comment 1 min read PEM vs. PKCS#12 (P12/PFX): Understanding the Difference Between Certificate Formats Pascal Reitermann Pascal Reitermann Pascal Reitermann Follow Dec 26 '25 PEM vs. PKCS#12 (P12/PFX): Understanding the Difference Between Certificate Formats # security # devops # webdev # java 1 reaction Comments Add Comment 3 min read I built a Python tool to hunt down Remote Access Trojans on Windows MentalistOps MentalistOps MentalistOps Follow Dec 29 '25 I built a Python tool to hunt down Remote Access Trojans on Windows # python # security # cybersecurity # software Comments Add Comment 1 min read Building Cryptographic Audit Trails for SEC Rule 17a-4: A Technical Deep Dive VeritasChain Standards Organization (VSO) VeritasChain Standards Organization (VSO) VeritasChain Standards Organization (VSO) Follow Dec 24 '25 Building Cryptographic Audit Trails for SEC Rule 17a-4: A Technical Deep Dive # security # fintech # python # cryptography Comments Add Comment 9 min read Building a Secure CI/CD Pipeline: Or How I Learned to Stop Worrying and Love DevSecOps Mano Nagarajan Mano Nagarajan Mano Nagarajan Follow Dec 30 '25 Building a Secure CI/CD Pipeline: Or How I Learned to Stop Worrying and Love DevSecOps # devsecops # cicd # security # devops Comments Add Comment 9 min read Securing IoT: Best Practices for Developers in a Smart-Device World 🔐🌍 Willie Harris Willie Harris Willie Harris Follow Dec 25 '25 Securing IoT: Best Practices for Developers in a Smart-Device World 🔐🌍 # iot # security # cybersecurity # devops 6 reactions Comments Add Comment 4 min read Is 'Shift Left' Just Another Buzzword? Rethinking Enterprise Security in 2026 Barecheck Team Barecheck Team Barecheck Team Follow Dec 25 '25 Is 'Shift Left' Just Another Buzzword? Rethinking Enterprise Security in 2026 # devsecops # shiftleft # security # cicd Comments Add Comment 4 min read OSI Layer 4—The Steward Narnaiezzsshaa Truong Narnaiezzsshaa Truong Narnaiezzsshaa Truong Follow Dec 26 '25 OSI Layer 4—The Steward # osi # security # ai # aiops Comments Add Comment 4 min read Practical MCP-Style Authorization: An Experimental PoC and Guide Aniket Hingane Aniket Hingane Aniket Hingane Follow Dec 24 '25 Practical MCP-Style Authorization: An Experimental PoC and Guide # security # authorization # python # tutorial Comments Add Comment 16 min read Ethereum-Solidity Quiz Q5: What is a Private Mempool? MihaiHng MihaiHng MihaiHng Follow Dec 26 '25 Ethereum-Solidity Quiz Q5: What is a Private Mempool? # blockchain # security # monitoring # ethereum 1 reaction Comments Add Comment 1 min read Configure it Out with AWS AgentCore and Kiro mgbec mgbec mgbec Follow for AWS Community Builders Dec 30 '25 Configure it Out with AWS AgentCore and Kiro # security # amazonbedrock # aiagent # kiro Comments Add Comment 5 min read Critical Security Vulnerability in React Server Components Brijesh Dobariya Brijesh Dobariya Brijesh Dobariya Follow for CodedThemes Dec 25 '25 Critical Security Vulnerability in React Server Components # nextjs # javascript # security # react Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/t/ai/page/75#main-content | Artificial Intelligence Page 75 - 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 Artificial Intelligence Follow Hide Artificial intelligence leverages computers and machines to mimic the problem-solving and decision-making capabilities found in humans and in nature. Create Post submission guidelines Posts about artificial intelligence. Older #ai posts 72 73 74 75 76 77 78 79 80 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Lessons from running the same debugging prompt through different AI systems Rohit Gavali Rohit Gavali Rohit Gavali Follow Dec 23 '25 Lessons from running the same debugging prompt through different AI systems # webdev # programming # ai Comments Add Comment 8 min read Should we stop using AI for Software Development? Leon Revill Leon Revill Leon Revill Follow Jan 9 Should we stop using AI for Software Development? # ai # softwareengineering # leadership Comments Add Comment 9 min read How We Decide Whether AI Software Is Worth Paying For Rylko Roman Rylko Roman Rylko Roman Follow Dec 23 '25 How We Decide Whether AI Software Is Worth Paying For # ai # software # webdev # investing Comments Add Comment 5 min read How to Bypass reCAPTCHA and Turnstile in Crawlee with CapSolver luisgustvo luisgustvo luisgustvo Follow Dec 24 '25 How to Bypass reCAPTCHA and Turnstile in Crawlee with CapSolver # ai # automation # bypass # webdev Comments Add Comment 7 min read Stop Flattening Your Images: How Qwen2-VL Unlocks "Layered" Vision Juddiy Juddiy Juddiy Follow Dec 23 '25 Stop Flattening Your Images: How Qwen2-VL Unlocks "Layered" Vision # webdev # ai # python # web3 3 reactions Comments Add Comment 4 min read AI Engineering: Advent of AI with goose Day 14 - Complete Operations System Erica Erica Erica Follow Dec 22 '25 AI Engineering: Advent of AI with goose Day 14 - Complete Operations System # ai # goose # adventofai # programming 1 reaction Comments Add Comment 5 min read Practical Observations from Real-World Software Development in the Age of AI Fahad TEch Fahad TEch Fahad TEch Follow Jan 6 Practical Observations from Real-World Software Development in the Age of AI # discuss # ai # productivity # softwareengineering Comments Add Comment 1 min read Kilo Code Weekly Product Roundup Darko from Kilo Darko from Kilo Darko from Kilo Follow Dec 23 '25 Kilo Code Weekly Product Roundup # coding # product # ai Comments Add Comment 3 min read Qwen Image 2512 Workflow: Complete Guide to AI Image Generation in 2026 Garyvov Garyvov Garyvov Follow Jan 5 Qwen Image 2512 Workflow: Complete Guide to AI Image Generation in 2026 # ai # deeplearning # opensource # tutorial Comments Add Comment 11 min read Data Science & AI: A Developer’s Guide to the Future of Analytics Software Developer Software Developer Software Developer Follow Dec 23 '25 Data Science & AI: A Developer’s Guide to the Future of Analytics # ai # datascience # analytics # futurechallenge 1 reaction Comments Add Comment 5 min read Fabrice Bellard Releases MicroQuickJS Aman Shekhar Aman Shekhar Aman Shekhar Follow Dec 24 '25 Fabrice Bellard Releases MicroQuickJS # ai # machinelearning # techtrends Comments Add Comment 5 min read AI in Web Development: Real Changes, Use Cases, and Limits rukmini santoshi rukmini santoshi rukmini santoshi Follow Dec 23 '25 AI in Web Development: Real Changes, Use Cases, and Limits # webdev # ai # aiinwebdevelopment # webdevelopmen Comments Add Comment 8 min read 📊 2026-01-05 - Daily Intelligence Recap - Top 3 Signals Agent_Asof Agent_Asof Agent_Asof Follow Jan 5 📊 2026-01-05 - Daily Intelligence Recap - Top 3 Signals # tech # programming # startup # ai Comments Add Comment 4 min read A Senior Engineer’s Guide to Securing and Scaling Model Context Protocol (MCP) OnlineProxy OnlineProxy OnlineProxy Follow Dec 22 '25 A Senior Engineer’s Guide to Securing and Scaling Model Context Protocol (MCP) # programming # ai # beginners # tutorial Comments Add Comment 7 min read How the Creator of Claude Code Actually Uses It Ashok Naik Ashok Naik Ashok Naik Follow Jan 6 How the Creator of Claude Code Actually Uses It # ai # productivity # claudecode # devtools 1 reaction Comments Add Comment 3 min read New to this Community Salman Ahmad Salman Ahmad Salman Ahmad Follow Dec 24 '25 New to this Community # webdev # programming # ai # javascript Comments Add Comment 1 min read Stop Paying for OpenAI: Build Your Own Local RAG Pipeline in Python- a PDF Chatbot Niyati Gupta Niyati Gupta Niyati Gupta Follow Dec 28 '25 Stop Paying for OpenAI: Build Your Own Local RAG Pipeline in Python- a PDF Chatbot # ai # python 1 reaction Comments Add Comment 11 min read Speedrun your AI coding workflow.⚡️ rx76d rx76d rx76d Follow Dec 23 '25 Speedrun your AI coding workflow.⚡️ # ai # productivity # opensource # npm Comments Add Comment 1 min read Boosting Developer Productivity with AI: What the Data Really Says Fay Fay Fay Follow Dec 27 '25 Boosting Developer Productivity with AI: What the Data Really Says # ai # productivity # developers # programming Comments Add Comment 3 min read The Hidden Costs of Inefficient AI Agents (And How to Fix Them) shashank agarwal shashank agarwal shashank agarwal Follow Dec 24 '25 The Hidden Costs of Inefficient AI Agents (And How to Fix Them) # webdev # ai # programming # devops Comments 1 comment 2 min read Architecting Enterprise grade Multi‑Agent AI with AWS Strands & Amazon Bedrock AgentCore Seenivasa Ramadurai Seenivasa Ramadurai Seenivasa Ramadurai Follow Dec 27 '25 Architecting Enterprise grade Multi‑Agent AI with AWS Strands & Amazon Bedrock AgentCore # architecture # ai # agents # aws 2 reactions Comments Add Comment 7 min read Rule of Two Piece Mathew Pregasen Mathew Pregasen Mathew Pregasen Follow Dec 24 '25 Rule of Two Piece # ai # security # llm # authorization Comments 1 comment 7 min read Qwen-Image-2512 vs. Z-Image Turbo: 5-Prompt Benchmark - Which Model is Better? Garyvov Garyvov Garyvov Follow Jan 5 Qwen-Image-2512 vs. Z-Image Turbo: 5-Prompt Benchmark - Which Model is Better? # ai # performance # promptengineering Comments Add Comment 5 min read How I Built a Stroke Capture System for an AI Drawing Game Adam Adam Adam Follow Dec 22 '25 How I Built a Stroke Capture System for an AI Drawing Game # showdev # gamedev # webdev # ai Comments Add Comment 2 min read THE SKETCH Lisa Girlinghouse Lisa Girlinghouse Lisa Girlinghouse Follow Jan 6 THE SKETCH # ai # devchallenge # machinelearning # portfolio Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/askrishnapravin/for-loop-vs-map-for-making-multiple-api-calls-3lhd#main-content | for loop vs .map() for making multiple API calls - 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 Krishna Pravin Posted on May 14, 2020 • Edited on May 29, 2020 for loop vs .map() for making multiple API calls # javascript # api # async Promise / async-await is used for making API calls. const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/1` ) const todo = await response . json () console . log ( todo ) Enter fullscreen mode Exit fullscreen mode Assuming I have a list of ids of todo items and I want the title of all them then I shall use the below snippet inside an async function const todoIdList = [ 1 , 2 , 3 , 4 ] for ( const id of todoIdList ) { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) } Enter fullscreen mode Exit fullscreen mode This same can be written with any of these for , for...in , for...of loops. Assuming each API request arbitrarily takes 100ms exactly, the total time taken for getting the details of four todo items will have to be greater than 400ms if we use any of the above-mentioned loops. This execution time can be drastically reduced by using .map() . const todoIdList = [ 1 , 2 , 3 , 4 ] await Promise . all ( todoIdList . map ( async ( id ) => { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) }) ) Enter fullscreen mode Exit fullscreen mode Adding timers const todoIdList = [ 1 , 2 , 3 , 4 ] console . time ( ' for {} ' ); for ( const id of todoIdList ) { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) } console . timeEnd ( ' for {} ' ); console . time ( ' .map() ' ); await Promise . all ( todoIdList . map ( async ( id ) => { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) }) ) console . timeEnd ( ' .map() ' ); Enter fullscreen mode Exit fullscreen mode The Reason for loop for loop goes to the next iteration only after the whole block's execution is completed. In the above scenario only after both the promises(await) gets resolved , for loop moves to the next iteration and makes the API call for the next todo item. .map() .map() moves on to the next item as soon as a promise is returned . It does not wait until the promise is resolved. In the above scenario, .map() does not wait until the response for todo items comes from the server. It makes all the API calls one by one and for each API call it makes, a respective promise is returned. Promise.all waits until all of these promises are resolved. async/await is syntactic sugar for Promises It will be more clear if the same code is written without async/await const todoIdList = [ 1 , 2 , 3 , 4 ] console . time ( ' .map() ' ) Promise . all ( todoIdList . map ( id => { return new Promise (( resolve ) => { fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) . then ( response => { return new Promise (() => { response . json () . then ( todo => { console . log ( todo . title ) resolve () }) }) }) }) }) ) . then (() => { console . timeEnd ( ' .map() ' ); }) Enter fullscreen mode Exit fullscreen mode It is not possible to mimic the respective code for for loop by replacing async/await with Promises because, the control which triggers the next iteration will have to written within the .then() block. This piece of code will have to be created within the JS engine. All the snippets are working code, you can try it directly in the browser console. Note: snippets need to be enclosed within an async function except for the last one use Axios or any other suitable library if fetch is not available. Let me know if there is an even better and easy/short way of making API calls. Also, do not forget to mention any mistakes I've made or tips, suggestions to improve this content. Top comments (6) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Quinn Quinn Quinn Follow Joined Jun 28, 2021 • Jun 28 '21 Dropdown menu Copy link Hide Not really a fair comparison. Map is creating a new array of promises then asynchronously executing them. To do this with a for loop you would do something like this: const todoIdList = [1, 2, 3, 4] const promiseList = [] for (const id of todoIdList) { const response = fetch( https://jsonplaceholder.typicode.com/todos/${id} ) promiseList.push(response.json()) } const responses = Promise.all(promiseList) Like comment: Like comment: 5 likes Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Jul 26 '21 Dropdown menu Copy link Hide This approach looks good. Pushing the promises into an array within for loop will achieve concurrency. But when we have a need for more than one await inside the block, it will not work. In the above code, response.json() won't work because response is a promise, it won't have json() method. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Yogendra Yogendra Yogendra Follow Location Bengaluru, India Work Web Developer at LayerIV Joined Sep 25, 2020 • Jan 31 '21 Dropdown menu Copy link Hide This is quite great. But, could you tell me what is the optimum way to resolve multiple promises and get their statuses, as Promise.all() fails as soon as any of the Promise rejects? I heard of Promise.allSettled() but is only available in recent versions of ES. Thanks!! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Feb 9 '21 Dropdown menu Copy link Hide Shim: npmjs.com/package/promise.allsettled Polyfill: logic24by7.com/promise-allsettled-... Like comment: Like comment: Like Comment button Reply Collapse Expand Rajesh Moka Rajesh Moka Rajesh Moka Follow I am a front end developer. I like building stuff with react. Location India Work Front End Developer at Tata Consultancy Services Joined May 27, 2020 • Jan 20 '21 Dropdown menu Copy link Hide This is a great article. I had trouble understanding the last example without async await but with promises. I knew promise.all takes promises array as an argument, but why did we write promise in each fetch call? Can u explain a little Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Jan 29 '21 Dropdown menu Copy link Hide The last example(using promise) is the same as the previous one(using await). We have a promise inside fetch because parsing response as json response.json() returns a promise. For each API call, Promise.all() will first wait for the API call's response to arrive, and then it will wait for the json parsing to complete. When Promise.all takes an array of promises, it will wait for all the inner promises as well to get resolved. 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 Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 Trending on DEV Community Hot Top 7 Featured DEV Posts of the Week # top7 # discuss Stop Overengineering: How to Write Clean Code That Actually Ships 🚀 # discuss # javascript # programming # webdev If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://docs.python.org/id/3/ | 3.14.2 Documentation Tema Otomatis Terang Gelap Unduh Unduh dokumen-dokumen ini Dokumen menurut versi 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) Semua versi Sumber daya lain PEP Index Beginner's Guide Book List Audio/Visual Talks Python Developer’s Guide Navigasi index modul | Python » 3.14.2 Documentation » | Tema Otomatis Terang Gelap | Dokumentasi Python 3.14.2 Welcome! This is the official documentation for Python 3.14.2. Documentation sections: Apa yang baru di 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 HOWTOs 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 FAQs 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 Ikhtisar Terms explained Halaman pencarian 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 Hak cipta Tentang dokumentasi Unduh Unduh dokumen-dokumen ini Dokumen menurut versi 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) Semua versi Sumber daya lain PEP Index Beginner's Guide Book List Audio/Visual Talks Python Developer’s Guide « Navigasi index modul | Python » 3.14.2 Documentation » | Tema Otomatis Terang Gelap | © Hak cipta 2001 Python Software Foundation. Halaman ini dilisensikan di bawah Lisensi Python Software Foundation Versi 2. Contoh, resep, dan kode lainnya dalam dokumentasi juga dilisensikan di bawah Lisensi Zero Clause BSD. Lihat Sejarah dan Lisensi untuk informasi lebih lanjut. Python Software Foundation adalah sebuah korporasi nirlaba. Mari berdonasi. Terakhir diperbarui pada Jan 13, 2026 (06:38 UTC). Menemukan kekutu ? Dibuat menggunakan Sphinx 8.2.3. | 2026-01-13T08:49:04 |
https://python-docs-es.readthedocs.io/page/CONTRIBUTING.html | Guía para contribuir en la traducción — Documentación de Python en Español -- 3.13.0 Tema Auto Claro Oscuro Tabla de contenido Guía para contribuir en la traducción Paso 0: Configuración de Github Paso 1: ¿Qué archivo traducir? Paso 2: ¡Comienza a traducir! A tener en cuenta Previsualizar los cambios Memoria de traducción Esta página Reporta un bug Ver fuente Navegación índice módulos | Python » Documentación 3.13.0 » Guía para contribuir en la traducción | Tema Auto Claro Oscuro | Nota ¡Ayúdanos a traducir la documentación oficial de Python al Español! Puedes encontrar más información en Como contribuir . Ayuda a acercar Python a más personas de habla hispana. Guía para contribuir en la traducción ¶ ¡Muchas gracias por tu interés en participar de la traducción de la documentación oficial de Python al Español! Este es el grupo de trabajo para la traducción de la documentación oficial de Python al Español, todo el contenido de la traducción es mantenido por voluntaries que aportan su tiempo y trabajo a la comunidad. Antes de comenzar tu primera traducción, y que sigas con esta guia de contribución, queremos señalar algunos lineamientos generales . Nota Si tienes cualquier duda, puedes enviarnos un email a docs-es @ python . org . También puedes unirte a nuestro canal de Telegram si necesitas ayuda. El proceso general de traducción son tres pasos, de los cuales el primero tendrás que realizar solo una vez. Te los detallamos a continuación. Paso 0: Configuración de Github ¶ Esta configuración la tienes que realizar sólo una vez, y con ello podrás realizar todas las contribuciones que quieras. Para enviar una traducción, necesitas tener un fork del repositorio oficial, haciendo click en el botón encerrado en rojo. Nota Puedes consular la ayuda oficial de GitHub , si lo deseas. Clona el fork del repositorio que acabas de crear: git clone git @github . com : < TU - USUARIO >/ python - docs - es . git Ingresa en la carpeta que git clone creó en tu computadora: cd python - docs - es / Agrega el repositorio original como «upstream»: git remote add upstream https : // github . com / python / python - docs - es . git (Opcional) Crea un entorno virtual y actívalo: python - m venv venv source venv / bin / activate # macOS y Linux venv \ Scripts \ activate . bat # Windows (Opcional) Instala los requerimientos del proyecto: pip install - r requirements - own . txt Nota Al tener instalado los requerimientos, podrás utilizas las herramientas powrap y pospell para poder verificar tus archivos traducidos, y también construir la documentación localmente. Paso 1: ¿Qué archivo traducir? ¶ Tenemos una lista de issues en GitHub en dónde vamos coordinando el trabajo realizado para no traducir dos veces lo mismo. El proceso para traducir un archivo es el siguiente: Elige cualquiera de los issues que no están asignados a otra persona. Deja un comentario en el issue diciendo que quieres trabajar en él. Espera a que un administrador te asigne el issue. ¡Empieza a traducir! Paso 2: ¡Comienza a traducir! ¶ Tener un archivo asignado para traducir . Verifica que estás en la rama principal del repositorio, 3.13 (esto es muy importante para evitar crear una nueva rama a partir de una traducción anterior): git checkout 3.13 Crea una rama nueva en base al artículo en el que vayas a trabajar. Por ejemplo, si vas a trabajar en el archivo library/ast.po , usa un nombre similar a: git checkout - b traduccion - ast Una vez que hayas elegido el archivo, lo puedes abrir con el editor poedit y empezar a traducir. Formato de columnas : Si utilizas poedit es posible que tu archivo tenga la estructura adecuada, pero te invitamos a comprobarlo con la herramienta powrap , la cual puedes instalar y utilizar por la línea de comandos. Ejecuta: powrap < directorio >/ tu_archivo . po Recuerda que tu archivo puede estar dentro de un <directorio> , como library , con lo que tendrás que ejecutar el comando powrap library/tu_archivo.po si no te encuentras en el mismo directorio de tu archivo. Nota Si estás en Windows y tienes problemas, mira los comentarios de Utilizar powrap en Windows para más información. Nota En 3.13 notamos un problema de inconsistencia en las versiones de powrap que podrían ser utilizadas, con lo que la verificación del CI fue deshabilitada, pero te recomendamos que puedas ejecutar powrap localmente de todas formas. Corrección ortográfica : Para verificar la ortografía de tu archivo puedes utilizar la herramienta pospell para que verifiques que todas las palabras están aceptadas o incluidas en diccionarios. Para ello tenemos un script de conveniencia que puedes utilizar: python scripts / check_spell . py < directorio >/ tu_archivo . po Si alguna palabra no es reconocida, y es una palabra válida, tienes que agregarla al diccionario correspondiente en el directorio dictionaries/. Busca el archivo que corresponde al que estás traduciendo y si no existe, créalo. Por ejemplo el diccionario del archivo library/ast.po se encuentra en dictionaries/library_ast.po . Nota Si estás en Windows y tienes problemas, mira los comentarios de Utilizar pospell en Windows para más información. Nota En 3.13 los trozos de código ahora pueden ser traducidos, con lo cual esperamos que puedas traducir solo los comentarios de dichos códigos. Es probable que check_spell.py falle con algunas entradas, esto se debe a que pospell (docutils) no tienen compatibilidad para entender líneas de código. La solución temporal es no traducir las entradas que check_spell.py genere errores con el mensaje Unexpected identation . Cuando hayas terminado tu sesión, debes guardar tus cambios y enviarlos a GitHub (No olvides añadir tu nombre al archivo TRANSLATORS ). Si estuvieras trabajando en el archivo library/ast.po los pasos serían: git add library / ast . po git commit - m 'Traducido archivo library/ast' git push origin traduccion - ast Nota Mira los mensajes que el último comando imprimirá por pantalla, pues encontrarás un enlace para abrir un nuevo Pull-request directamente. Puedes consultar la ayuda oficial de GitHub para crear un Pull Request si lo deseas. En la descripción de la Pull Request escribe Closes #<número de issue> (así se cierra automáticamente cuando se hace merge ) Nota Si hace tiempo que venis trabajando en una traducción es importante mantener actualizada tu copia local antes de realizar el Pull Request . A tener en cuenta ¶ Esta traducción es mantenida por personas de todo el mundo que hablan el idioma Español. No queremos atarla a ninguna región en particular y creemos que es un valor extra la diversidad de la misma. Vas a encontrar secciones con diferentes tonalidades de países, regiones o estilos. Lo único que pedimos es consistencia dentro de un mismo módulo o sección (es decir no cambiar de estilo de un párrafo a otro, por ejemplo) y siempre intentar que la persona del otro lado pueda entender lo que estamos escribiendo (no usar lunfardo o regionalismos muy propios de un único lugar). En muchos casos el mejor criterio es pensar en el vocabulario que utilizamos cuando le explicamos a otra persona, o en el trabajo. En muchas ocasiones la versión en inglés o “spanglish” de la palabra es mucho mejor que decir “git unir” (para git merge). Siempre vas a tener una revisión de lo que propongas y en ese intercambio otras personas van a ayudarte a destrabar las dudas que tengas. Colaborar haciendo revisiones también es muy muy importante, así que si tienes un rato libre puedes comenzar por mirar los PRs pendientes de revisar. (mira la Guía del revisor ) La documentación es ENORME, cualquier traba que encuentres siempre puedes marcar el texto como «fuzzy» o para revisar en el futuro. No pierdas horas buscando la palabra perfecta. No debes traducir el contenido de :ref:... , :term:... , :dfn:... , etc. Si tienes que usar palabras en inglés debes ponerlas en cursiva (rodeadas por asteriscos) Puedes revisar las Preguntas Frecuentes para leer sobre problemas conocidos. Si traduces un título que es un enlace , por favor traduce el link también (por ejemplo un artículo a Wikipedia). En caso de que no haya una traducción del artículo en Wikipedia deja el título sin traducir. Si tienes una duda sobre una palabra o término , escríbelo como mejor suene para vos y marca ese párrafo como «Need work» / «Necesita trabajo» en poedit . Además, escribe un comentario explicando cuál es el termino en ese párrafo con el que no estabas segura. Puedes usar la traducción al Portugués para ver cómo ellos hicieron la traducción de alguna palabra. Wikipedia puede ser útil también. Busca la palabra en Inglés, y luego mira si tiene una traducción al Español en la barra de la izquierda. Suelen estar bastante bien explicados. Te recomendamos abrir una Pull Request aunque sea en formato borrador (marcada como draft) desde los primeros commits de la traducción de tu fichero. De esta forma, puedes recibir feedback desde el principio que puedes aplicar al resto de la traducción, y probar el build más a menudo. Último pero no menos importante, divertite y contá con la ayuda de todes . Te esperamos en nuestro chat en telegram. ¡Gracias! Previsualizar los cambios ¶ Una vez que hayas hecho un Pull Request en GitHub, este mostrará al final de página una sección de «check». Allí debería haber uno que diga docs/readthedocs.org:python-docs-es y al lado un link de «Details». Haciendo click en ese link verás una versión de la documentación completa que incluirá todos tus cambios. Tendrás que navegar hasta el archivo que hayas cambiado para ver cómo se visualiza luego del build. Memoria de traducción ¶ Tenemos una Memoria de Traducción , que usamos para tener consistencia con algunos términos. Si tienes alguna duda respecto a cómo traducir alguna palabra no te olvides de revisar este contenido. Del mismo modo, si luego de trabajar sobre un término complicado llegas a un acuerdo con otros colaboradores: no se olviden de agregarlo. Tabla de contenido Guía para contribuir en la traducción Paso 0: Configuración de Github Paso 1: ¿Qué archivo traducir? Paso 2: ¡Comienza a traducir! A tener en cuenta Previsualizar los cambios Memoria de traducción Esta página Reporta un bug Ver fuente « Navegación índice módulos | Python » Documentación 3.13.0 » Guía para contribuir en la traducción | Tema Auto Claro Oscuro | © Derechos de autor 2001-2026, 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. Hospedado en Read the Docs . La Python Software Foundation es una corporación sin fines de lucro. Por favor dona. Última actualización en Jan 06, 2026 (16:10 UTC). Encontraste un bug ? Creado usando Sphinx 8.0.2. | 2026-01-13T08:49:04 |
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:49:04 |
https://reactnative.dev/ | React Native · Learn once, write anywhere Skip to main content Re-watch the latest React Native Keynote from React Conf 2025 React Native Development Guides Components APIs Architecture Contributing Community Showcase Blog <path fill=currentColor d="M12,9c1.65,0,3,1.35,3,3s-1.35,3-3,3s-3-1.35-3-3S10.35,9,12,9 M12,7c-2.76,0-5,2.24-5,5s2.24,5,5,5s5-2.24,5-5 S14.76,7 | 2026-01-13T08:49:04 |
https://dev.to/t/distribution/page/3 | Distribution 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 # distribution Follow Hide getting music out there Create Post Older #distribution posts 1 2 3 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/datalaria/weather-service-project-part-2-building-the-interactive-frontend-with-github-pages-or-netlify-ho1#2-reacting-to-user-selection | Weather Service Project (Part 2): Building the Interactive Frontend with GitHub Pages or Netlify and JavaScript - 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 Daniel for Datalaria Posted on Jan 13 • Originally published at datalaria.com Weather Service Project (Part 2): Building the Interactive Frontend with GitHub Pages or Netlify and JavaScript # javascript # webdev # tutorial # frontend In the first part of this series , we laid the groundwork for our global weather service. We built a Python script to fetch weather data from OpenWeatherMap, efficiently stored it in city-specific CSV files, and automated the entire collection process using GitHub Actions. Our "robot" is diligently gathering data 24/7. But what good is data if you can't see it? Today, we shift our focus to the frontend : building an interactive, user-friendly dashboard that allows anyone to explore the weather data we've collected. We'll leverage the power of static site hosting with GitHub Pages or Netlify , use "vanilla" JavaScript to bring it to life, and rely on some excellent libraries for data handling and visualization. Let's make our data shine! Free Web Hosting: GitHub Pages vs. Netlify The first hurdle for any web project is hosting. Traditional servers can be costly and complex to manage. Following our "serverless and free" philosophy, both GitHub Pages and Netlify are perfect solutions for hosting static websites directly from your GitHub repository. Option 1: GitHub Pages GitHub Pages allows you to host static websites directly from your GitHub repository. Activation is trivial: Go to Settings > Pages in your repository. Select your main branch (or the branch containing your web content) as the source. Choose the /root folder (or a /docs folder if you prefer) as the location of your web files. Click Save . And just like that, your index.html file (and any linked assets) becomes publicly accessible at a URL like https://your-username.github.io/your-repository-name/ . Simple, effective, and free! 🚀 Option 2: Netlify (the final choice for this project!) For this project, I ultimately opted for Netlify due to its flexibility, ease of managing custom domains, and integrated continuous deployment. It also allows me to host the project directly under my Datalaria domain ( https://datalaria.com/apps/weather/ ). Steps to deploy on Netlify: Connect Your Repository : Log in to Netlify. Click "Add new site" then "Import an existing project". Connect your GitHub account and select your Weather Service project repository. Deployment Configuration : Owner : Your GitHub account. Branch to deploy : main (or the branch where your frontend code resides). Base directory : Leave this empty if your index.html and assets are in the root of the repository, or specify a subfolder if applicable (e.g., /frontend ). Build command : Leave it empty, as our frontend is purely static with no build step required (no frameworks like React/Vue). Publish directory : . (or the subfolder containing your static files, e.g., /frontend ). Deploy Site : Click "Deploy site". Netlify will fetch your repository, deploy it, and provide you with a random URL. Custom Domain (Optional but recommended) : To use a domain like datalaria.com/apps/weather/ : Go to Site settings > Domain management > Domains > Add a custom domain . Follow the steps to add your domain and configure it with your provider's DNS (by adding CNAME or A records). For the specific path ( /apps/weather/ ), you would typically configure a "subfolder" or "base URL" within your application if it's not directly at the root of the domain. In this case, our index.html is designed to be served from a subpath. Netlify handles this transparently once the site is deployed and your domain is configured. It's that simple! Each git push to your configured branch will trigger a new deployment on Netlify, keeping your dashboard always up-to-date. The Frontend Tech Stack: HTML, CSS, and JavaScript (with a little help) For this dashboard, I opted for a lightweight approach: plain HTML for structure, a bit of CSS for styling, and "vanilla" JavaScript (without complex frameworks) for interactivity. To handle specific tasks, I incorporated two fantastic libraries: PapaParse.js : The fastest in-browser CSV parser for JavaScript. It's the bridge between our raw CSV files and the JavaScript data structures we need for visualization. Chart.js : A powerful and flexible JavaScript charting library that makes creating beautiful, responsive, and interactive charts incredibly easy. The Dashboard Logic: Bringing Data to Life in index.html Our index.html acts as the main canvas, orchestrating the fetching, parsing, and rendering of weather data. 1. Dynamic City Loading In stead of hardcoding a list of cities, we want our dashboard to automatically update if we add new cities in the backend. We achieve this by fetching a simple ciudades.txt file (containing one city name per line) and dynamically populating a <select> dropdown element using JavaScript's fetch API. const citySelector = document . getElementById ( ' citySelector ' ); let myChart = null ; // Global variable to store the Chart.js instance async function loadCityList () { try { const response = await fetch ( ' ciudades.txt ' ); const text = await response . text (); // Filter out empty lines from the text file const cities = text . split ( ' \n ' ). filter ( line => line . trim () !== '' ); cities . forEach ( city => { const option = document . createElement ( ' option ' ); option . value = city ; option . textContent = city ; citySelector . appendChild ( option ); }); // Load the first city by default when the page initializes if ( cities . length > 0 ) { loadAndDrawData ( cities [ 0 ]); } } catch ( error ) { console . error ( ' Error loading city list: ' , error ); // Optional: Display a user-friendly error message } } // Trigger city loading when the DOM is fully loaded document . addEventListener ( ' DOMContentLoaded ' , loadCityList ); Enter fullscreen mode Exit fullscreen mode 2. Reacting to User Selection When a user selects a city from the dropdown, we need to respond immediately. An addEventListener on the <select> element detects the change event and calls our main function to fetch and draw the data for the newly selected city. citySelector . addEventListener ( ' change ' , ( event ) => { const selectedCity = event . target . value ; loadAndDrawData ( selectedCity ); }); Enter fullscreen mode Exit fullscreen mode 3. Fetching, Parsing, and Drawing Data This is the central function where everything comes to life. It is responsible for: Constructing the URL for the specific city's CSV file (e.g., data/Leon.csv ). Using Papa.parse to download and process the CSV content directly in the browser. PapaParse handles asynchronous fetching and parsing, making it incredibly easy. Extracting relevant labels (dates) and data (temperatures) from the parsed CSV for Chart.js. Crucial! : Before drawing a new chart, we must destroy the previous Chart.js instance ( if (myChart) { myChart.destroy(); } ). Forgetting this step leads to overlapping charts and performance issues! 💥 Creating a new Chart() instance with the updated data. Additionally, it calls a function to load and display the AI prediction for that city, seamlessly integrating it into the dashboard. function loadAndDrawData ( city ) { const csvUrl = `datos/ ${ city } .csv` ; // Note the 'datos/' folder from Part 1 const ctx = document . getElementById ( ' weatherChart ' ). getContext ( ' 2d ' ); Papa . parse ( csvUrl , { download : true , // Tells PapaParse to download the file header : true , // Treats the first row as headers skipEmptyLines : true , complete : function ( results ) { const weatherData = results . data ; // Extract labels (dates) and data (temperatures) const labels = weatherData . map ( row => row . fecha_hora . split ( ' ' )[ 0 ]); // Extract only the date const maxTemp = weatherData . map ( row => parseFloat ( row . temp_max_c )); const minTemp = weatherData . map ( row => parseFloat ( row . temp_min_c )); // Destroy the previous chart instance if it exists to prevent overlaps if ( myChart ) { myChart . destroy (); } // Create a new Chart.js instance myChart = new Chart ( ctx , { type : ' line ' , data : { labels : labels , datasets : [{ label : `Max Temp (°C) - ${ city } ` , data : maxTemp , borderColor : ' rgb(255, 99, 132) ' , tension : 0.1 }, { label : `Min Temp (°C) - ${ city } ` , data : minTemp , borderColor : ' rgb(54, 162, 235) ' , tension : 0.1 }] }, options : { // Chart options for responsiveness, title, etc. responsive : true , maintainAspectRatio : false , scales : { y : { beginAtZero : false } }, plugins : { legend : { position : ' top ' }, title : { display : true , text : `Historical Weather Data for ${ city } ` } } } }); // Load and display AI prediction loadPrediction ( city ); }, error : function ( err , file ) { console . error ( " Error parsing CSV: " , err , file ); // Optional: display a user-friendly error message on the dashboard if ( myChart ) { myChart . destroy (); } // Clear chart if loading fails } }); } Enter fullscreen mode Exit fullscreen mode 4. Displaying AI Predictions The integration of AI predictions (which we'll delve into in Part 3) is also managed from the frontend. The backend generates a predicciones.json file, and our JavaScript simply fetches this JSON, finds the prediction for the selected city, and displays it. async function loadPrediction ( city ) { const predictionElement = document . getElementById ( ' prediction ' ); try { const response = await fetch ( ' predicciones.json ' ); const predictions = await response . json (); if ( predictions && predictions [ city ]) { predictionElement . textContent = `Max Temp. Prediction for tomorrow: ${ predictions [ city ]. toFixed ( 1 )} °C` ; } else { predictionElement . textContent = ' Prediction not available. ' ; } } catch ( error ) { console . error ( ' Error loading predictions: ' , error ); predictionElement . textContent = ' Error loading prediction. ' ; } } Enter fullscreen mode Exit fullscreen mode Conclusion (Part 2) We've transformed raw data into an engaging and interactive experience! By combining static hosting from GitHub Pages or Netlify, "vanilla" JavaScript for logic, PapaParse.js for CSV handling, and Chart.js for beautiful visualizations, we've built a powerful frontend that is both free and highly effective. The dashboard now provides immediate insight into the historical weather patterns of any selected city. But what about the future? In the third and final part of this series , we'll delve into the exciting world of Machine Learning to add a predictive layer to our service. We'll explore how to use historical data to forecast tomorrow's weather, turning our service into a true weather "oracle." Stay tuned! References and Links of Interest: Complete Web Service : You can see the final project in action here: https://datalaria.com/apps/weather/ Project GitHub Repository : Explore the source code and project structure in my repository: https://github.com/Dalaez/app_weather PapaParse.js : Fast in-browser CSV parser for JavaScript: https://www.papaparse.com/ Chart.js : Simple, yet flexible JavaScript charting for designers & developers: https://www.chartjs.org/ GitHub Pages : Official documentation on how to host your sites: https://docs.github.com/en/pages Netlify : Official Netlify website: https://www.netlify.com/ 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 Datalaria Follow More from Datalaria Weather Service Project (Part 1): Building the Data Collector with Python and GitHub Actions or Netlify # api # automation # python # tutorial Proyecto Weather Service (Parte 1): Construyendo el Recolector de Datos con Python y GitHub Actions o Netlify # dataengineering # python # spanish # tutorial Building Datalaria: Technologies and Tools # showdev # github # tooling # webdev 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://www.chartjs.org/ | Chart.js | Open source HTML5 Charts for your website Chart.js Simple yet flexible JavaScript charting library for the modern web Get Started Samples Ecosystem GitHub New in 4.0 Colors plugin Default palette of Chart.js brand colors is available as a built-in time-saving zero-configuration plugin. New in 4.0 Tree-shaking JavaScript bundle size can be reduced by dozens of kilobytes by registering only necessary components . New in 3.5 Scale stacking Layout boxes can be stacked and weighted in groups. New in 3.4 Subtitle plugin A secondary title plugin with all the same options as main title. New in 3.1 Line segment styling Line segments can be styled by any user defined criteria. New in 3.0 Advanced animations Transitions of every property in every element can be configured individually and independently. New in 3.0 Performance! Numerous performance enhancements have been introduced. This example has 1M (2x500k) points with the new decimation plugin enabled. New in 2.0 Mixed chart types Mix and match bar and line charts to provide a clear visual distinction between datasets. New in 2.0 New chart axis types Plot complex, sparse datasets on date time, logarithmic or even entirely custom scales with ease. New in 2.0 Animate everything! Out of the box stunning transitions when changing data, updating colours and adding datasets. Open source Chart.js is a community maintained project, contributions welcome! 8 Chart types Visualize your data in 8 different ways; each of them animated and customisable. HTML5 Canvas Great rendering performance across all modern browsers (IE11+). Responsive Redraws charts on window resize for perfect scale granularity. Find Chart.js on GitHub or Read detailed documentation Chart.js was built from the hard work of all these contributors. | 2026-01-13T08:49:04 |
https://gg.forem.com/t/nintendo | Nintendo - Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close # nintendo Follow Hide Mario, Zelda, and all things Nintendo Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The Game Theorists: Game Theory: How DEADLY Is Donkey Kong's Punch? Gaming News Gaming News Gaming News Follow Oct 8 '25 The Game Theorists: Game Theory: How DEADLY Is Donkey Kong's Punch? # nintendo # nintendoswitch # retrogaming # pcgaming Comments Add Comment 1 min read Jeju Island Pokémon GO Stamp Rally Map Pinning Jun Jun Jun Follow Oct 24 '25 Jeju Island Pokémon GO Stamp Rally Map Pinning # walkthroughs # openworld # mobilegaming # nintendo 3 reactions Comments Add Comment 2 min read IGN: Pokémon 'Teraleak' Reveals Franchise's Plans Through 2030 - IGN Daily Fix Gaming News Gaming News Gaming News Follow Oct 16 '25 IGN: Pokémon 'Teraleak' Reveals Franchise's Plans Through 2030 - IGN Daily Fix # nintendo # xbox # pcgaming # gamedev 1 reaction Comments Add Comment 1 min read IGN: The Biggest Game Releases of October 2025 Gaming News Gaming News Gaming News Follow Sep 27 '25 IGN: The Biggest Game Releases of October 2025 # pcgaming # nintendo # playstation # xbox Comments Add Comment 1 min read GameSpot: Hollow Knight: Silksong Review Gaming News Gaming News Gaming News Follow Sep 26 '25 GameSpot: Hollow Knight: Silksong Review # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Pokemon TCG: Mega Evolution - Official Launch Trailer Gaming News Gaming News Gaming News Follow Sep 26 '25 IGN: Pokemon TCG: Mega Evolution - Official Launch Trailer # boardgames # nintendo Comments Add Comment 1 min read IGN: Silent Hill f: First 36 Minutes of Gameplay (4K, 60 FPS) Gaming News Gaming News Gaming News Follow Sep 26 '25 IGN: Silent Hill f: First 36 Minutes of Gameplay (4K, 60 FPS) # pcgaming # nintendo Comments Add Comment 1 min read IGN: Pokémon Legends: Z-A – The Final Preview Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Pokémon Legends: Z-A – The Final Preview # nintendo # nintendoswitch Comments Add Comment 1 min read GameSpot: Hyrule Warriors: Age of Imprisonment Is Adding A Lot More Depth To Combat Gaming News Gaming News Gaming News Follow Sep 25 '25 GameSpot: Hyrule Warriors: Age of Imprisonment Is Adding A Lot More Depth To Combat # nintendo # nintendoswitch # pcgaming # gamedev Comments Add Comment 1 min read IGN: Cyberpunk 2077: Ultimate Edition - Official ‘New Ways to Play’ Nintendo Switch 2 Trailer Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Cyberpunk 2077: Ultimate Edition - Official ‘New Ways to Play’ Nintendo Switch 2 Trailer # nintendo # nintendoswitch # pcgaming # playstation Comments Add Comment 1 min read IGN: Hollow Knight: Silksong Boss Fight - Cogwork Dancers (Choral Chambers) Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Hollow Knight: Silksong Boss Fight - Cogwork Dancers (Choral Chambers) # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Hades 2 Full Release: First 15 Minutes of Nintendo Switch 2 Gameplay (4K 60FPS) Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Hades 2 Full Release: First 15 Minutes of Nintendo Switch 2 Gameplay (4K 60FPS) # nintendo # nintendoswitch # pcgaming # indie Comments Add Comment 1 min read IGN: Hades 2 Review Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Hades 2 Review # pcgaming # nintendoswitch # nintendo # indie Comments Add Comment 1 min read IGN: Phoenix Wright Ace Attorney Trilogy - Official Update Trailer | TGS 2025 Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Phoenix Wright Ace Attorney Trilogy - Official Update Trailer | TGS 2025 # pcgaming # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Monster Hunter Stories 3: Twisted Reflection - Official Release Date Trailer | TGS 2025 Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Monster Hunter Stories 3: Twisted Reflection - Official Release Date Trailer | TGS 2025 # nintendo # nintendoswitch # pcgaming # playstation Comments Add Comment 1 min read GameSpot: Pokemon Legends: Z-A Takes The Series In A Bold Direction Gaming News Gaming News Gaming News Follow Sep 24 '25 GameSpot: Pokemon Legends: Z-A Takes The Series In A Bold Direction # gaming # nintendo Comments Add Comment 1 min read GameSpot: Pokemon Legends: Z-A - 22 Biggest Changes Gaming News Gaming News Gaming News Follow Sep 24 '25 GameSpot: Pokemon Legends: Z-A - 22 Biggest Changes # nintendo Comments Add Comment 1 min read IGN: Hollow Knight: Silksong - How to Make It Through Bilewater Gaming News Gaming News Gaming News Follow Sep 20 '25 IGN: Hollow Knight: Silksong - How to Make It Through Bilewater # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Is Nintendo Switch 2 Off to a Good Start? - NVC Clips Gaming News Gaming News Gaming News Follow Sep 20 '25 IGN: Is Nintendo Switch 2 Off to a Good Start? - NVC Clips # nintendo # nintendoswitch # gamedev Comments Add Comment 1 min read IGN: Nintendo Switch 2’s First 100 Days Report Card - Next-Gen Console Watch Gaming News Gaming News Gaming News Follow Sep 20 '25 IGN: Nintendo Switch 2’s First 100 Days Report Card - Next-Gen Console Watch # nintendo # nintendoswitch # gamedev Comments Add Comment 1 min read IGN: Sonic Racing: CrossWorlds Review Gaming News Gaming News Gaming News Follow Sep 20 '25 IGN: Sonic Racing: CrossWorlds Review # pcgaming # playstation # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: It’s Expensive Being a Nintendo Fan in 2025 - NVC Clips Gaming News Gaming News Gaming News Follow Sep 19 '25 IGN: It’s Expensive Being a Nintendo Fan in 2025 - NVC Clips # nintendo # nintendoswitch 1 reaction Comments Add Comment 1 min read IGN: Dying Light: The Beast - Tutorial, First Boss, & First Open World Moments Gaming News Gaming News Gaming News Follow Sep 19 '25 IGN: Dying Light: The Beast - Tutorial, First Boss, & First Open World Moments # pcgaming # nintendo 4 reactions Comments Add Comment 1 min read IGN: Donkey Kong Bananza: DK Island and Emerald Rush Review Gaming News Gaming News Gaming News Follow Sep 19 '25 IGN: Donkey Kong Bananza: DK Island and Emerald Rush Review # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read IGN: Hollow Knight Silksong - How to Get the Double Jump (Faydown Cloak) Gaming News Gaming News Gaming News Follow Sep 19 '25 IGN: Hollow Knight Silksong - How to Get the Double Jump (Faydown Cloak) # pcgaming # indie # nintendo 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 Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:49:04 |
https://docs.python.org/3/license.html#history-of-the-software | 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:49:04 |
https://gg.forem.com/t/cloudgaming | Cloudgaming - Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close # cloudgaming Follow Hide Streaming games without the hardware hassle Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu My First game - Comms Under Fire Shaquille Niekerk Shaquille Niekerk Shaquille Niekerk Follow Dec 11 '25 My First game - Comms Under Fire # gamedev # indie # cloudgaming # singleplayer 8 reactions Comments 3 comments 1 min read 🎮 Puzzleet: Algorithm Practice Meets Puzzle Gaming Andriy Kudelya Andriy Kudelya Andriy Kudelya Follow Nov 7 '25 🎮 Puzzleet: Algorithm Practice Meets Puzzle Gaming # gamedev # mobilegaming # cloudgaming 3 reactions Comments 1 comment 1 min read Yes, Reality Labs is still losing billions Gaming News Gaming News Gaming News Follow Aug 5 '25 Yes, Reality Labs is still losing billions # gaminghardware # vrgaming # gameaccessories # cloudgaming Comments Add Comment 1 min read Xbox Is Still Figuring Out How To Market Its PC Games, And Has Come Up With Another Pointless Name Change Gaming News Gaming News Gaming News Follow Aug 5 '25 Xbox Is Still Figuring Out How To Market Its PC Games, And Has Come Up With Another Pointless Name Change # xbox # pcgaming # gamepass # cloudgaming Comments Add Comment 1 min read Xbox 1st party costs are not included in Gamepass so they can claim it's profitable. Gaming News Gaming News Gaming News Follow Jul 14 '25 Xbox 1st party costs are not included in Gamepass so they can claim it's profitable. # browsergames # pcgaming # multiplayer # cloudgaming Comments 1 comment 1 min read Xbox 1st party costs are not included in Gamepass so they can claim it's profitable. Gaming News Gaming News Gaming News Follow Jul 10 '25 Xbox 1st party costs are not included in Gamepass so they can claim it's profitable. # browsergames # pcgaming # cloudgaming # gaminghardware Comments Add Comment 1 min read IGN: Arkane Studios Founder Takes Shots at Microsoft's Xbox Game Pass - IGN Daily Fix Gaming News Gaming News Gaming News Follow Jul 8 '25 IGN: Arkane Studios Founder Takes Shots at Microsoft's Xbox Game Pass - IGN Daily Fix # gamepass # xbox # gamedev # cloudgaming Comments Add Comment 1 min read Over 6,000 people have lost their jobs at Xbox in less than two years Gaming News Gaming News Gaming News Follow Jul 7 '25 Over 6,000 people have lost their jobs at Xbox in less than two years # xbox # pcgaming # gaminghardware # cloudgaming Comments Add Comment 1 min read European game publisher group responds to Stop Killing Games, claims "These proposals would curtail developer choice" Gaming News Gaming News Gaming News Follow Jul 7 '25 European game publisher group responds to Stop Killing Games, claims "These proposals would curtail developer choice" # pcgaming # gamedev # steam # cloudgaming Comments Add Comment 1 min read loading... trending guides/resources 🎮 Puzzleet: Algorithm Practice Meets Puzzle Gaming My First game - Comms Under Fire 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:49:04 |
https://docs.python.org/3/license.html#asynchronous-socket-services | 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:49:04 |
https://dev.to/rsionnach/shift-left-reliability-4poo#main-content | Shift-Left Reliability - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Rob Fox Posted on Jan 12 Shift-Left Reliability # sre # devops # cicd # platformengineering We've become exceptionally good at incident response. Modern teams restore service quickly, run thoughtful postmortems, and hold themselves accountable through corrective actions. And yet… A team ships a change that passes every test, gets all the required approvals, and still brings down checkout for 47 minutes. The postmortem conclusion? "We should have known our latency SLO was already at 94% before deploying." Many postmortems point to the same root cause: changes we introduced ourselves. Not hardware failures. Not random outages. Just software behaving exactly as we told it to. We continue to treat reliability as something to evaluate once those changes are already live. This isn't a failure of tooling or process. It's a question of when we decide whether a system is ready. The paradox We've invested heavily in observing and responding to failure - better alerting, faster incident response, thorough postmortems. Teams care deeply about reliability and spend significant time optimizing how they respond to incidents. But when in a service's lifecycle are they supposed to define reliability? Where's the innovation that happens before deployment? Where reliability decisions actually happen today I've seen multiple teams running identical technology stacks with completely different SLOs, metrics, and alerts. Nobody told them what to implement, what's best-practice or how to tune their alerts. They want to be good reliability citizens, but getting from the theory in the handbook to putting that theory into practice is not straightforward. Services regularly move into production with SLOs being created months later - or never. Dashboards are missing, insufficient, or inconsistent. "Looks fine to me" during PR reviews. Tribal knowledge. Varying levels of understanding across teams. Reliability is fundamentally bespoke and ungoverned. That's the core issue. The missing layer GitHub gave us version control for code. Terraform gave us version control for infrastructure. Security has transformed with shift-left - finding flaws as code is written, not after deployment. We're still missing version control for reliability. We need a specification that defines requirements, validates them against reality, and generates the artifacts: dashboards, SLOs, alerts, escalation policies. If the specification is validated and the artifacts created, the same tool can check in real-time whether a service is in breach - and block high-risk deployments in CI/CD. What shift-left reliability actually means Shift-left reliability doesn't mean more alerts and dashboards, more postmortems or more people in the room. It means: Spec - Define reliability requirements as code before production deployment Validate - Test those requirements against reality Enforce - Gate deployments through CI/CD Engineers don't write PromQL or Grafana JSON - they declare intent, and reliability becomes deterministic. Outcomes are predictable, consistent, transparent, and follow best practice. An executable reliability contract Keep it simple. A team creates a service.yaml file with their reliability intent: name: payment-api tier: critical type: api team: payments dependencies: - postgresql - redis Enter fullscreen mode Exit fullscreen mode Here is a complete service.yaml example . Tooling validates metrics, SLOs, and error budgets then generates these artifacts automatically. This is the approach I am exploring with an open-source project called NthLayer. NthLayer runs in any CI/CD pipeline - GitHub Actions, ArgoCD, Jenkins, Tekton, GitLab CI. The goal isn't to be an inflexible blocker; it's visible risk and explicit decisions. Overrides are fine when they're intentional, logged, and owned. When a deployment is attempted, the specification is evaluated against reality: $ nthlayer check-deploy - service payment-api ERROR: Deployment blocked - availability SLO at 99.2% (target: 99.95%) - error budget exhausted: -47 minutes remaining - 3 P1 incidents in last 7 days Exit code: 2 (BLOCKED) Enter fullscreen mode Exit fullscreen mode Why now? SLOs have had 8+ years to mature and move from the Google SRE Handbook into mainstream practice. GitOps has normalized declarative configuration. Platform Engineering has matured as a discipline. The concepts are ready but the tooling has lagged behind. This is a deliberate shift in approach. Reliability is no longer up for debate during incidents. Services have defined owners with deterministic standards. We can stop reinventing the reliability wheel every time a new service is onboarded. If requirements change, update the service.yaml , run NthLayer and every service benefits from adopting the new standard. What this does not replace NthLayer doesn't replace service catalogs, developer portals, observability platforms, or incident management. It doesn't predict failures or eliminate human judgment. It's upstream of all these systems. The goal: a reliability specification, automated deployment gates and to reduce cognitive load to implement best practices. Open questions I don't have all the answers but two questions I keep returning to are: Contract Drift: What happens when the spec says 99.95% but reality has been 99.5% for months? Is the contract wrong, or is the service broken? Emergency Overrides: How should they work? Who approves? How do you prevent them from becoming the default? The timing problem Where do reliability decisions actually happen in your organization? What would it look like to decide readiness before deployment? What reliability rules do you wish you could enforce automatically? The timing problem isn't going away. The only question is whether you address it before deployment - or learn about it in the postmortem. NthLayer is open source and looking for early adopters. If you're tired of reliability being an afterthought: pip install nthlayer nthlayer init nthlayer check-deploy --service your-service Enter fullscreen mode Exit fullscreen mode → github.com/rsionnach/nthlayer Star the repo, open an issue, or tell me I'm wrong. I want to hear how reliability decisions happen in your organization. Rob Fox is a Senior Site Reliability Engineer focused on platform and reliability tooling. He's exploring how reliability engineering can move earlier in the software delivery lifecycle. Find him on GitHub . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Rob Fox Follow Sr Site Reliability Engineer. Building NthLayer, an open-source tool for shift-left reliability. Opinions are my own. github.com/rsionnach Location Dublin, Ireland Joined Jan 6, 2026 Trending on DEV Community Hot The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning How I Built an AI Terraform Review Agent on Serverless AWS # aws # terraform # serverless # devops How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://wantuil.com | Ed Wantuil - Criando, Compartilhando e Evoluindo Ed Wantuil Criando. Compartilhando. Evoluindo. Meu objetivo é compartilhar conhecimento, criar soluções e ajudar outras pessoas a evoluírem na carreira de tecnologia. LinkedIn GitHub Artigos YouTube (34) 99214-2011 [email protected] | 2026-01-13T08:49:04 |
https://dev.to/x0x7b | 0x7b - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions 0x7b 404 bio not found Joined Joined on Jan 12, 2026 github website More info about @x0x7b Post 1 post published Comment 0 comments written Tag 0 tags followed Observing Behavioral Anomalies in Web Applications Beyond Signature Scanners 0x7b 0x7b 0x7b Follow Jan 12 Observing Behavioral Anomalies in Web Applications Beyond Signature Scanners # monitoring # performance # security # testing Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://docs.python.org/3/license.html#cnri-license-agreement-for-python-1-6-1 | 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:49:04 |
https://docs.python.org/fr/3/ | 3.14.2 Documentation Thème Auto Clair Sombre Téléchargement Téléchargement de ces documentations Docs par version 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) Toutes les versions Autres ressources PEP Index Beginner's Guide Book List Audio/Visual Talks Python Developer’s Guide Navigation index modules | Python » 3.14.2 Documentation » | Thème Auto Clair Sombre | Documentation Python 3.14.2 Bienvenue sur la documentation officielle de Python 3.14.2. Rubriques : Quoi de neuf dans Python 3.14 ? Ou toutes les nouveautés depuis Python 2.0 Tutoriel Commencez par ici : une découverte de la syntaxe et des fonctionnalités de Python Référence de la bibliothèque Bibliothèque standard Référence du langage Syntaxe et les éléments du langage Installer et utiliser Python Comment installer, configurer, et utiliser Python Les HOWTOs de Python Manuels spécialisés Installer des modules Python Modules tiers et PyPI.org Distribuer des modules Python Publier des modules pour que d'autres puissent les installer Extension et intégration Pour les développeurs C/C++ L'API C de Python Référence de l'API en C FAQs Foire aux questions (avec les réponses !) Obsolescence Fonctionnalité obsolètes Index, glossaire, et recherche : Index global des modules Tous les modules et bibliothèques Index général Toutes les fonctions, classes et termes Glossaire Jargon expliqué Page de recherche Recherche dans cette documentation Table des matières complète Liste complète des rubriques et sous-rubriques Autour du projet : Signalement de bogue Contribuer à la documentation Télécharger cette documentation Histoire et licence de Python Copyright À propos de la documentation Téléchargement Téléchargement de ces documentations Docs par version 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) Toutes les versions Autres ressources PEP Index Beginner's Guide Book List Audio/Visual Talks Python Developer’s Guide « Navigation index modules | Python » 3.14.2 Documentation » | Thème Auto Clair Sombre | © Copyright 2001 Python Software Foundation. La licence de cette page est la Python Software Foundation License Version 2. La licence des exemples, recettes, et autres morceaux de code se trouvant dans la documentation est la Zero Clause BSD License. Pour plus d'informations, consultez Histoire et licence . La Python Software Foundation est une association à but non lucratif. Elle vit de vos dons. Dernière mise à jour : janv. 13, 2026 (06:30 UTC). Un bogue ? Crée par Sphinx 8.2.3. | 2026-01-13T08:49:04 |
https://peps.python.org/pep-0257/ | PEP 257 – Docstring Conventions | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 257 Toggle light / dark / auto colour theme PEP 257 – Docstring Conventions Author : David Goodger <goodger at python.org>, Guido van Rossum <guido at python.org> Discussions-To : Doc-SIG list Status : Active Type : Informational Created : 29-May-2001 Post-History : 13-Jun-2001 Table of Contents Abstract Rationale Specification What is a Docstring? One-line Docstrings Multi-line Docstrings Handling Docstring Indentation Copyright Acknowledgements Abstract This PEP documents the semantics and conventions associated with Python docstrings. Rationale The aim of this PEP is to standardize the high-level structure of docstrings: what they should contain, and how to say it (without touching on any markup syntax within docstrings). The PEP contains conventions, not laws or syntax. “A universal convention supplies all of maintainability, clarity, consistency, and a foundation for good programming habits too. What it doesn’t do is insist that you follow it against your will. That’s Python!” —Tim Peters on comp.lang.python, 2001-06-16 If you violate these conventions, the worst you’ll get is some dirty looks. But some software (such as the Docutils docstring processing system PEP 256 , PEP 258 ) will be aware of the conventions, so following them will get you the best results. Specification What is a Docstring? A docstring is a string literal that occurs as the first statement in a module, function, class, or method definition. Such a docstring becomes the __doc__ special attribute of that object. All modules should normally have docstrings, and all functions and classes exported by a module should also have docstrings. Public methods (including the __init__ constructor) should also have docstrings. A package may be documented in the module docstring of the __init__.py file in the package directory. String literals occurring elsewhere in Python code may also act as documentation. They are not recognized by the Python bytecode compiler and are not accessible as runtime object attributes (i.e. not assigned to __doc__ ), but two types of extra docstrings may be extracted by software tools: String literals occurring immediately after a simple assignment at the top level of a module, class, or __init__ method are called “attribute docstrings”. String literals occurring immediately after another docstring are called “additional docstrings”. Please see PEP 258 , “Docutils Design Specification”, for a detailed description of attribute and additional docstrings. For consistency, always use """triple double quotes""" around docstrings. Use r"""raw triple double quotes""" if you use any backslashes in your docstrings. There are two forms of docstrings: one-liners and multi-line docstrings. One-line Docstrings One-liners are for really obvious cases. They should really fit on one line. For example: def kos_root (): """Return the pathname of the KOS root directory.""" global _kos_root if _kos_root : return _kos_root ... Notes: Triple quotes are used even though the string fits on one line. This makes it easy to later expand it. The closing quotes are on the same line as the opening quotes. This looks better for one-liners. There’s no blank line either before or after the docstring. The docstring is a phrase ending in a period. It prescribes the function or method’s effect as a command (“Do this”, “Return that”), not as a description; e.g. don’t write “Returns the pathname …”. The one-line docstring should NOT be a “signature” reiterating the function/method parameters (which can be obtained by introspection). Don’t do: def function ( a , b ): """function(a, b) -> list""" This type of docstring is only appropriate for C functions (such as built-ins), where introspection is not possible. However, the nature of the return value cannot be determined by introspection, so it should be mentioned. The preferred form for such a docstring would be something like: def function ( a , b ): """Do X and return a list.""" (Of course “Do X” should be replaced by a useful description!) Multi-line Docstrings Multi-line docstrings consist of a summary line just like a one-line docstring, followed by a blank line, followed by a more elaborate description. The summary line may be used by automatic indexing tools; it is important that it fits on one line and is separated from the rest of the docstring by a blank line. The summary line may be on the same line as the opening quotes or on the next line. The entire docstring is indented the same as the quotes at its first line (see example below). Insert a blank line after all docstrings (one-line or multi-line) that document a class – generally speaking, the class’s methods are separated from each other by a single blank line, and the docstring needs to be offset from the first method by a blank line. The docstring of a script (a stand-alone program) should be usable as its “usage” message, printed when the script is invoked with incorrect or missing arguments (or perhaps with a “-h” option, for “help”). Such a docstring should document the script’s function and command line syntax, environment variables, and files. Usage messages can be fairly elaborate (several screens full) and should be sufficient for a new user to use the command properly, as well as a complete quick reference to all options and arguments for the sophisticated user. The docstring for a module should generally list the classes, exceptions and functions (and any other objects) that are exported by the module, with a one-line summary of each. (These summaries generally give less detail than the summary line in the object’s docstring.) The docstring for a package (i.e., the docstring of the package’s __init__.py module) should also list the modules and subpackages exported by the package. The docstring for a function or method should summarize its behavior and document its arguments, return value(s), side effects, exceptions raised, and restrictions on when it can be called (all if applicable). Optional arguments should be indicated. It should be documented whether keyword arguments are part of the interface. The docstring for a class should summarize its behavior and list the public methods and instance variables. If the class is intended to be subclassed, and has an additional interface for subclasses, this interface should be listed separately (in the docstring). The class constructor should be documented in the docstring for its __init__ method. Individual methods should be documented by their own docstring. If a class subclasses another class and its behavior is mostly inherited from that class, its docstring should mention this and summarize the differences. Use the verb “override” to indicate that a subclass method replaces a superclass method and does not call the superclass method; use the verb “extend” to indicate that a subclass method calls the superclass method (in addition to its own behavior). Do not use the Emacs convention of mentioning the arguments of functions or methods in upper case in running text. Python is case sensitive and the argument names can be used for keyword arguments, so the docstring should document the correct argument names. It is best to list each argument on a separate line. For example: def complex ( real = 0.0 , imag = 0.0 ): """Form a complex number. Keyword arguments: real -- the real part (default 0.0) imag -- the imaginary part (default 0.0) """ if imag == 0.0 and real == 0.0 : return complex_zero ... Unless the entire docstring fits on a line, place the closing quotes on a line by themselves. This way, Emacs’ fill-paragraph command can be used on it. Handling Docstring Indentation Docstring processing tools will strip a uniform amount of indentation from the second and further lines of the docstring, equal to the minimum indentation of all non-blank lines after the first line. Any indentation in the first line of the docstring (i.e., up to the first newline) is insignificant and removed. Relative indentation of later lines in the docstring is retained. Blank lines should be removed from the beginning and end of the docstring. Since code is much more precise than words, here is an implementation of the algorithm: def trim ( docstring ): if not docstring : return '' # Convert tabs to spaces (following the normal Python rules) # and split into a list of lines: lines = docstring . expandtabs () . splitlines () # Determine minimum indentation (first line doesn't count): indent = sys . maxsize for line in lines [ 1 :]: stripped = line . lstrip () if stripped : indent = min ( indent , len ( line ) - len ( stripped )) # Remove indentation (first line is special): trimmed = [ lines [ 0 ] . strip ()] if indent < sys . maxsize : for line in lines [ 1 :]: trimmed . append ( line [ indent :] . rstrip ()) # Strip off trailing and leading blank lines: while trimmed and not trimmed [ - 1 ]: trimmed . pop () while trimmed and not trimmed [ 0 ]: trimmed . pop ( 0 ) # Return a single string: return ' \n ' . join ( trimmed ) The docstring in this example contains two newline characters and is therefore 3 lines long. The first and last lines are blank: def foo (): """ This is the second line of the docstring. """ To illustrate: >>> print repr ( foo . __doc__ ) '\n This is the second line of the docstring.\n ' >>> foo . __doc__ . splitlines () ['', ' This is the second line of the docstring.', ' '] >>> trim ( foo . __doc__ ) 'This is the second line of the docstring.' Once trimmed, these docstrings are equivalent: def foo (): """A multi-line docstring. """ def bar (): """ A multi-line docstring. """ Copyright This document has been placed in the public domain. Acknowledgements The “Specification” text comes mostly verbatim from PEP 8 by Guido van Rossum. This document borrows ideas from the archives of the Python Doc-SIG . Thanks to all members past and present. Source: https://github.com/python/peps/blob/main/peps/pep-0257.rst Last modified: 2024-04-17 11:35:59 GMT Contents Abstract Rationale Specification What is a Docstring? One-line Docstrings Multi-line Docstrings Handling Docstring Indentation Copyright Acknowledgements Page Source (GitHub) | 2026-01-13T08:49:04 |
https://dev.to/datalaria/weather-service-project-part-2-building-the-interactive-frontend-with-github-pages-or-netlify-ho1#option-1-github-pages | Weather Service Project (Part 2): Building the Interactive Frontend with GitHub Pages or Netlify and JavaScript - 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 Daniel for Datalaria Posted on Jan 13 • Originally published at datalaria.com Weather Service Project (Part 2): Building the Interactive Frontend with GitHub Pages or Netlify and JavaScript # javascript # webdev # tutorial # frontend In the first part of this series , we laid the groundwork for our global weather service. We built a Python script to fetch weather data from OpenWeatherMap, efficiently stored it in city-specific CSV files, and automated the entire collection process using GitHub Actions. Our "robot" is diligently gathering data 24/7. But what good is data if you can't see it? Today, we shift our focus to the frontend : building an interactive, user-friendly dashboard that allows anyone to explore the weather data we've collected. We'll leverage the power of static site hosting with GitHub Pages or Netlify , use "vanilla" JavaScript to bring it to life, and rely on some excellent libraries for data handling and visualization. Let's make our data shine! Free Web Hosting: GitHub Pages vs. Netlify The first hurdle for any web project is hosting. Traditional servers can be costly and complex to manage. Following our "serverless and free" philosophy, both GitHub Pages and Netlify are perfect solutions for hosting static websites directly from your GitHub repository. Option 1: GitHub Pages GitHub Pages allows you to host static websites directly from your GitHub repository. Activation is trivial: Go to Settings > Pages in your repository. Select your main branch (or the branch containing your web content) as the source. Choose the /root folder (or a /docs folder if you prefer) as the location of your web files. Click Save . And just like that, your index.html file (and any linked assets) becomes publicly accessible at a URL like https://your-username.github.io/your-repository-name/ . Simple, effective, and free! 🚀 Option 2: Netlify (the final choice for this project!) For this project, I ultimately opted for Netlify due to its flexibility, ease of managing custom domains, and integrated continuous deployment. It also allows me to host the project directly under my Datalaria domain ( https://datalaria.com/apps/weather/ ). Steps to deploy on Netlify: Connect Your Repository : Log in to Netlify. Click "Add new site" then "Import an existing project". Connect your GitHub account and select your Weather Service project repository. Deployment Configuration : Owner : Your GitHub account. Branch to deploy : main (or the branch where your frontend code resides). Base directory : Leave this empty if your index.html and assets are in the root of the repository, or specify a subfolder if applicable (e.g., /frontend ). Build command : Leave it empty, as our frontend is purely static with no build step required (no frameworks like React/Vue). Publish directory : . (or the subfolder containing your static files, e.g., /frontend ). Deploy Site : Click "Deploy site". Netlify will fetch your repository, deploy it, and provide you with a random URL. Custom Domain (Optional but recommended) : To use a domain like datalaria.com/apps/weather/ : Go to Site settings > Domain management > Domains > Add a custom domain . Follow the steps to add your domain and configure it with your provider's DNS (by adding CNAME or A records). For the specific path ( /apps/weather/ ), you would typically configure a "subfolder" or "base URL" within your application if it's not directly at the root of the domain. In this case, our index.html is designed to be served from a subpath. Netlify handles this transparently once the site is deployed and your domain is configured. It's that simple! Each git push to your configured branch will trigger a new deployment on Netlify, keeping your dashboard always up-to-date. The Frontend Tech Stack: HTML, CSS, and JavaScript (with a little help) For this dashboard, I opted for a lightweight approach: plain HTML for structure, a bit of CSS for styling, and "vanilla" JavaScript (without complex frameworks) for interactivity. To handle specific tasks, I incorporated two fantastic libraries: PapaParse.js : The fastest in-browser CSV parser for JavaScript. It's the bridge between our raw CSV files and the JavaScript data structures we need for visualization. Chart.js : A powerful and flexible JavaScript charting library that makes creating beautiful, responsive, and interactive charts incredibly easy. The Dashboard Logic: Bringing Data to Life in index.html Our index.html acts as the main canvas, orchestrating the fetching, parsing, and rendering of weather data. 1. Dynamic City Loading In stead of hardcoding a list of cities, we want our dashboard to automatically update if we add new cities in the backend. We achieve this by fetching a simple ciudades.txt file (containing one city name per line) and dynamically populating a <select> dropdown element using JavaScript's fetch API. const citySelector = document . getElementById ( ' citySelector ' ); let myChart = null ; // Global variable to store the Chart.js instance async function loadCityList () { try { const response = await fetch ( ' ciudades.txt ' ); const text = await response . text (); // Filter out empty lines from the text file const cities = text . split ( ' \n ' ). filter ( line => line . trim () !== '' ); cities . forEach ( city => { const option = document . createElement ( ' option ' ); option . value = city ; option . textContent = city ; citySelector . appendChild ( option ); }); // Load the first city by default when the page initializes if ( cities . length > 0 ) { loadAndDrawData ( cities [ 0 ]); } } catch ( error ) { console . error ( ' Error loading city list: ' , error ); // Optional: Display a user-friendly error message } } // Trigger city loading when the DOM is fully loaded document . addEventListener ( ' DOMContentLoaded ' , loadCityList ); Enter fullscreen mode Exit fullscreen mode 2. Reacting to User Selection When a user selects a city from the dropdown, we need to respond immediately. An addEventListener on the <select> element detects the change event and calls our main function to fetch and draw the data for the newly selected city. citySelector . addEventListener ( ' change ' , ( event ) => { const selectedCity = event . target . value ; loadAndDrawData ( selectedCity ); }); Enter fullscreen mode Exit fullscreen mode 3. Fetching, Parsing, and Drawing Data This is the central function where everything comes to life. It is responsible for: Constructing the URL for the specific city's CSV file (e.g., data/Leon.csv ). Using Papa.parse to download and process the CSV content directly in the browser. PapaParse handles asynchronous fetching and parsing, making it incredibly easy. Extracting relevant labels (dates) and data (temperatures) from the parsed CSV for Chart.js. Crucial! : Before drawing a new chart, we must destroy the previous Chart.js instance ( if (myChart) { myChart.destroy(); } ). Forgetting this step leads to overlapping charts and performance issues! 💥 Creating a new Chart() instance with the updated data. Additionally, it calls a function to load and display the AI prediction for that city, seamlessly integrating it into the dashboard. function loadAndDrawData ( city ) { const csvUrl = `datos/ ${ city } .csv` ; // Note the 'datos/' folder from Part 1 const ctx = document . getElementById ( ' weatherChart ' ). getContext ( ' 2d ' ); Papa . parse ( csvUrl , { download : true , // Tells PapaParse to download the file header : true , // Treats the first row as headers skipEmptyLines : true , complete : function ( results ) { const weatherData = results . data ; // Extract labels (dates) and data (temperatures) const labels = weatherData . map ( row => row . fecha_hora . split ( ' ' )[ 0 ]); // Extract only the date const maxTemp = weatherData . map ( row => parseFloat ( row . temp_max_c )); const minTemp = weatherData . map ( row => parseFloat ( row . temp_min_c )); // Destroy the previous chart instance if it exists to prevent overlaps if ( myChart ) { myChart . destroy (); } // Create a new Chart.js instance myChart = new Chart ( ctx , { type : ' line ' , data : { labels : labels , datasets : [{ label : `Max Temp (°C) - ${ city } ` , data : maxTemp , borderColor : ' rgb(255, 99, 132) ' , tension : 0.1 }, { label : `Min Temp (°C) - ${ city } ` , data : minTemp , borderColor : ' rgb(54, 162, 235) ' , tension : 0.1 }] }, options : { // Chart options for responsiveness, title, etc. responsive : true , maintainAspectRatio : false , scales : { y : { beginAtZero : false } }, plugins : { legend : { position : ' top ' }, title : { display : true , text : `Historical Weather Data for ${ city } ` } } } }); // Load and display AI prediction loadPrediction ( city ); }, error : function ( err , file ) { console . error ( " Error parsing CSV: " , err , file ); // Optional: display a user-friendly error message on the dashboard if ( myChart ) { myChart . destroy (); } // Clear chart if loading fails } }); } Enter fullscreen mode Exit fullscreen mode 4. Displaying AI Predictions The integration of AI predictions (which we'll delve into in Part 3) is also managed from the frontend. The backend generates a predicciones.json file, and our JavaScript simply fetches this JSON, finds the prediction for the selected city, and displays it. async function loadPrediction ( city ) { const predictionElement = document . getElementById ( ' prediction ' ); try { const response = await fetch ( ' predicciones.json ' ); const predictions = await response . json (); if ( predictions && predictions [ city ]) { predictionElement . textContent = `Max Temp. Prediction for tomorrow: ${ predictions [ city ]. toFixed ( 1 )} °C` ; } else { predictionElement . textContent = ' Prediction not available. ' ; } } catch ( error ) { console . error ( ' Error loading predictions: ' , error ); predictionElement . textContent = ' Error loading prediction. ' ; } } Enter fullscreen mode Exit fullscreen mode Conclusion (Part 2) We've transformed raw data into an engaging and interactive experience! By combining static hosting from GitHub Pages or Netlify, "vanilla" JavaScript for logic, PapaParse.js for CSV handling, and Chart.js for beautiful visualizations, we've built a powerful frontend that is both free and highly effective. The dashboard now provides immediate insight into the historical weather patterns of any selected city. But what about the future? In the third and final part of this series , we'll delve into the exciting world of Machine Learning to add a predictive layer to our service. We'll explore how to use historical data to forecast tomorrow's weather, turning our service into a true weather "oracle." Stay tuned! References and Links of Interest: Complete Web Service : You can see the final project in action here: https://datalaria.com/apps/weather/ Project GitHub Repository : Explore the source code and project structure in my repository: https://github.com/Dalaez/app_weather PapaParse.js : Fast in-browser CSV parser for JavaScript: https://www.papaparse.com/ Chart.js : Simple, yet flexible JavaScript charting for designers & developers: https://www.chartjs.org/ GitHub Pages : Official documentation on how to host your sites: https://docs.github.com/en/pages Netlify : Official Netlify website: https://www.netlify.com/ 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 Datalaria Follow More from Datalaria Weather Service Project (Part 1): Building the Data Collector with Python and GitHub Actions or Netlify # api # automation # python # tutorial Proyecto Weather Service (Parte 1): Construyendo el Recolector de Datos con Python y GitHub Actions o Netlify # dataengineering # python # spanish # tutorial Building Datalaria: Technologies and Tools # showdev # github # tooling # webdev 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://www.python.org/community/sigs/retired | Retired SIGS | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Retired SIGS These are SIGs that existed in the past but are no longer active. Their archives and home pages are retained. A retired SIG can be revived, using the same criteria as for creating a new SIG. Name Coordinator Description Info catalog-sig A.M. Kuchling The Python software catalog archive March 2013 compiler-sig Jeremy Hylton Compiling and parsing Python Type checking, code generation archive May 2001 do-sig David Arnold Distributed Object Technologies archive August 2002 getopt-sig Greg Ward Argument parsing SIG archive February 2003 parser-sig A.M. Kuchling Parsing archive February 2003 persistence-sig Jeremy Hylton Persistence Framework for Python archive September 2003 plot-sig David Ascher Plotting and Graphing archive May 2001 thread-sig Greg Stein Process Threading archive May 2001 types-sig Paul Prescod Static Typing Design archive August 2002 string-sig Robin Friedrich String Processing archive March 2001 matrix-sig Paul Dubois Numerical Python archive January 2000 gui-sig Jim Fulton Graphical User Interface archive January 1999 objc-sig Jeff Sickel Objective-C viz Python archive January 1999 locator-sig Paul Everitt Python Resource Tracking (Software, docs, projects...). See the catalog-sig for a successor. archive January 1998 pattern-sig Dinu Gherman Idioms, Patterns, and Frameworks archive January 1998 progenv-sig Ken Manheimer Programming Environment archive January 1998 pythonwin-sig Mark Hammond Win95/NT GUI version of Python archive June 1997 uls-sig Duncan McGreggor Ultra Large-Scale systems and how such systems relate to Python. no archive available ... The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://dev.to/porus09 | Abhi - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Abhi More than human Joined Joined on Nov 26, 2025 github website More info about @porus09 Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 3 posts published Comment 0 comments written Tag 67 tags followed I Got Tired of Guessing JVM Performance — So I Built a Java Agent From Scratch 🚀 Abhi Abhi Abhi Follow Dec 17 '25 I Got Tired of Guessing JVM Performance — So I Built a Java Agent From Scratch 🚀 # webdev # programming # tutorial # productivity Comments Add Comment 3 min read Building vtracer: Day 1 – My First Java Agent Adventure with Java 21 Abhi Abhi Abhi Follow Dec 16 '25 Building vtracer: Day 1 – My First Java Agent Adventure with Java 21 # webdev # programming # java # tutorial Comments Add Comment 2 min read I Was Tired of Manual Video Editing — So I Built OmniVid Lite Abhi Abhi Abhi Follow Nov 28 '25 I Was Tired of Manual Video Editing — So I Built OmniVid Lite # webdev # ai # programming # javascript 1 reaction Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://peps.python.org/topic/governance/ | Governance PEPs | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » Governance PEPs Toggle light / dark / auto colour theme Governance PEPs Introduction This is the index of all Python Enhancement Proposals (PEPs) labelled under the ‘Governance’ topic. This is a sub-index of PEP 0 , the PEP index. These PEPs detail Python’s governance, including governance model proposals and selection, and the results of the annual steering council elections. Index by Category Process and Meta-PEPs PEP Title Authors PA 13 Python Language Governance The Python core team and community PA 545 Python Documentation Translations Julien Palard, Inada Naoki, Victor Stinner PA 609 Python Packaging Authority (PyPA) Governance Dustin Ingram, Pradyun Gedam, Sumana Harihareswara PA 729 Typing governance process Jelle Zijlstra, Shantanu Jain PA 731 C API Working Group Charter Guido van Rossum, Petr Viktorin, Victor Stinner, Steve Dower, Irit Katriel PA 732 The Python Documentation Editorial Board Joanna Jablonski PA 811 Defining Python Security Response Team membership and responsibilities Seth Michael Larson Other Informational PEPs PEP Title Authors IF 8000 Python Language Governance Proposal Overview Barry Warsaw IF 8002 Open Source Governance Survey Barry Warsaw, Łukasz Langa, Antoine Pitrou, Doug Hellmann, Carol Willing IA 8016 The Steering Council Model Nathaniel J. Smith, Donald Stufft IF 8100 January 2019 Steering Council election Nathaniel J. Smith, Ee Durbin IF 8101 2020 Term Steering Council election Ewa Jodlowska, Ee Durbin IF 8102 2021 Term Steering Council election Ewa Jodlowska, Ee Durbin, Joe Carey IF 8103 2022 Term Steering Council election Ewa Jodlowska, Ee Durbin, Joe Carey IF 8104 2023 Term Steering Council election Ee Durbin IF 8105 2024 Term Steering Council election Ee Durbin IF 8106 2025 Term Steering Council election Ee Durbin IF 8107 2026 Term Steering Council election Ee Durbin Open PEPs (under consideration) PEP Title Authors P 772 Packaging Council governance process Barry Warsaw, Deb Nicholson, Pradyun Gedam Historical Meta-PEPs and Informational PEPs PEP Title Authors PF 8001 Python Governance Voting Process Brett Cannon, Christian Heimes, Donald Stufft, Eric Snow, Gregory P. Smith, Łukasz Langa, Mariatta, Nathaniel J. Smith, Pablo Galindo Salgado, Raymond Hettinger, Tal Einat, Tim Peters, Zachary Ware Rejected, Superseded, and Withdrawn PEPs PEP Title Authors IR 8010 The Technical Leader Governance Model Barry Warsaw IR 8011 Python Governance Model Lead by Trio of Pythonistas Mariatta, Barry Warsaw IR 8012 The Community Governance Model Łukasz Langa IR 8013 The External Council Governance Model Steve Dower IR 8014 The Commons Governance Model Jack Jansen IR 8015 Organization of the Python community Victor Stinner PEP Types Key I — Informational : Non-normative PEP containing background, guidelines or other information relevant to the Python ecosystem P — Process : Normative PEP describing or proposing a change to a Python community process, workflow or governance S — Standards Track : Normative PEP with a new feature for Python, implementation change for CPython or interoperability standard for the ecosystem More info in PEP 1 . PEP Status Key A — Accepted : Normative proposal accepted for implementation A — Active : Currently valid informational guidance, or an in-use process D — Deferred : Inactive draft that may be taken up again at a later time <No letter> — Draft : Proposal under active discussion and revision F — Final : Accepted and implementation complete, or no longer active P — Provisional : Provisionally accepted but additional feedback needed R — Rejected : Formally declined and will not be accepted S — Superseded : Replaced by another succeeding PEP W — Withdrawn : Removed from consideration by sponsor or authors More info in PEP 1 . Contents Index by Category Process and Meta-PEPs Other Informational PEPs Open PEPs (under consideration) Historical Meta-PEPs and Informational PEPs Rejected, Superseded, and Withdrawn PEPs PEP Types Key PEP Status Key | 2026-01-13T08:49:04 |
https://dev.to/walteralleyz/why-portugal-can-be-your-next-career-step-4h38#comments | Why Portugal Can Be Your Next Career Step - 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 Walter Alleyz Posted on Jan 11 Why Portugal Can Be Your Next Career Step # career # international # workplace # braziliandevs Moving abroad can be a challenging career decision. Beyond that, there are many factors to consider: culture, people, convenience, quality of life, and what a new place can offer. Every detail can make a significant difference when deciding to take such a step. In this article, we will discuss the benefits of moving to Portugal in terms of career growth and professional potential. When You Hit a Career Plateau It is a common experience for almost every IT professional to face the question of how to continue evolving in their career. Many of us have already been through this phase and managed to move forward by learning new tools, studying and implementing new technologies, expanding our network, building connections, and attending workshops, among other strategies. However, there comes a point when our career hits a plateau. This often happens when you can no longer identify what to study next, how to increase your potential, or what steps to take to improve your salary. If this sounds familiar, it may be time to look abroad and seek opportunities to grow beyond the boundaries of technology itself. Why Moving to Portugal Is More Than a Lifestyle Choice The official language of Portugal is Portuguese, but you can hear many different languages spoken across the country. This is because Portugal is a popular tourist destination in Europe. You can easily find people who speak English. In addition, Portuguese people are known for their strong English skills, so you are unlikely to face communication barriers—especially if your goal is to improve your own communication skills. Beyond improving communication skills, you will be exposed to a wide range of cultures, including Portuguese culture itself—and this is an important factor to consider. Understanding different cultures is essential, as it helps you navigate diverse environments, collaborate more effectively with people from different backgrounds, and build stronger, more meaningful connections over time. Portugal also offers a wide variety of culinary options, with natural and healthy food easily found in any grocery store. People are warm and welcoming, and you will find yourself busy exploring natural parks and beautiful architecture throughout the country. Optimizing Your Social Profile to Attract International Companies “If you’re not visible, you won’t be found.” Preparing your social profile is the best choice when your goal is to move abroad. If you are using LinkedIn, the first step is to create a clear and meaningful title for your profession. For example, if you are a Business Analyst specializing in AI and BI, make that explicit. If you are a Java Developer with Cloud Computing experience, a title like Cloud Java Developer might be more effective. Choosing the right title makes it easier for headhunters to find you. The About section on LinkedIn is one of the most important parts of your profile. A strong About section should be concise, clear, and focused on your skills, achievements, and career goals. Start with a hook that grabs attention, then describe your experience, key accomplishments, and what you are passionate about. Take a look at a good example of an About section: “I am a Software Engineer specializing in Java and Python, with 5 years of experience building scalable web applications and cloud-based solutions. I have led teams of up to 4 developers and implemented projects that improved system performance by 30%. Currently, I am seeking opportunities abroad where I can leverage my technical expertise and leadership skills to drive impactful projects. Feel free to connect to discuss potential collaborations.” Organize experiences in reverse chronological order, starting with the most recent. Use bullet points to make it easy to read. A well-written About and Experience section significantly increases your chances of being discovered by headhunters and potential employers. Remember to write everything in English, since you are targeting the international market. Most importantly, focus on building meaningful connections: engage with people, show genuine interest in topics that matter, and make your objectives clear. Final Thoughts Feeling stuck in your career is a common experience for many IT professionals. It often occurs when you’re unsure of the next step, when acquiring more technical knowledge alone isn’t enough, and when it becomes necessary to seek new experiences beyond the tech bubble. In this article, I aimed to explain why Portugal is a great option for starting your international career, the benefits of living abroad, and the real impact it can have - both in terms of career growth and personal development. 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 Walter Alleyz Follow Location Brasil Education Software Engineering Work Developer Joined Oct 5, 2021 Trending on DEV Community Hot I Didn’t “Become” a Senior Developer. I Accumulated Damage. # programming # ai # career # discuss AI should not be in Code Editors # programming # ai # productivity # discuss Top 7 Featured DEV Posts of the Week # top7 # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/t/programming/page/77 | Programming Page 77 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 74 75 76 77 78 79 80 81 82 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Agent Knowledge vs Memories: Understanding the Difference Bobur Umurzokov Bobur Umurzokov Bobur Umurzokov Follow Jan 9 Agent Knowledge vs Memories: Understanding the Difference # webdev # programming # ai # productivity 1 reaction Comments Add Comment 5 min read An AI Almost Deleted My Code Alan Tsai Alan Tsai Alan Tsai Follow Dec 15 '25 An AI Almost Deleted My Code # ai # opensource # devtools # programming Comments 1 comment 4 min read The Go Build System: Optimised for Humans and Machines Gabor Koos Gabor Koos Gabor Koos Follow Jan 8 The Go Build System: Optimised for Humans and Machines # go # tutorial # webdev # programming 6 reactions Comments Add Comment 15 min read We’ve been shipping "slop" for 20 years. We just used to call it an MVP. GetPochi GetPochi GetPochi Follow Jan 9 We’ve been shipping "slop" for 20 years. We just used to call it an MVP. # discuss # programming # llm # ai Comments Add Comment 4 min read The Evolution of Java: From Enterprise Backbone to AI Enabler SYO SYO SYO Follow Dec 16 '25 The Evolution of Java: From Enterprise Backbone to AI Enabler # ai # java # programming Comments Add Comment 2 min read Your React Dashboard is Low-Bandwidth for LLMs Edward Burton Edward Burton Edward Burton Follow Dec 18 '25 Your React Dashboard is Low-Bandwidth for LLMs # webdev # ai # programming # devops 1 reaction Comments Add Comment 6 min read Coding Rust with Claude Code and Codex Tigran Bayburtsyan Tigran Bayburtsyan Tigran Bayburtsyan Follow Dec 29 '25 Coding Rust with Claude Code and Codex # rust # vibecoding # programming # ai 2 reactions Comments Add Comment 8 min read Hello world! Carlos Echeverría Carlos Echeverría Carlos Echeverría Follow Dec 17 '25 Hello world! # programming # webdev # javascript # react Comments Add Comment 1 min read Day 71: Python Three Sum – Two-Pointer O(n^2) Solution for Unique Zero-Sum Triplets (LeetCode #15 Vibes) Shahrouz Nikseresht Shahrouz Nikseresht Shahrouz Nikseresht Follow Dec 21 '25 Day 71: Python Three Sum – Two-Pointer O(n^2) Solution for Unique Zero-Sum Triplets (LeetCode #15 Vibes) # challenge # python # algorithms # programming Comments Add Comment 3 min read Docker, Beyond “It Works on My Machine” Anto Benil Anto Benil Anto Benil Follow Dec 30 '25 Docker, Beyond “It Works on My Machine” # programming # docker # softwareengineering # cloudnative 1 reaction Comments Add Comment 1 min read Getting Started with Flutter AI: App Dev Guide Nick Peterson Nick Peterson Nick Peterson Follow Dec 16 '25 Getting Started with Flutter AI: App Dev Guide # ai # flutter # programming # tutorial Comments Add Comment 4 min read Stop Buying Macs Just to Fix CSS Fabrizio La Rosa Fabrizio La Rosa Fabrizio La Rosa Follow Dec 15 '25 Stop Buying Macs Just to Fix CSS # webdev # programming # safari # css Comments Add Comment 3 min read Engineering a Multi-Capability MCP Server in Python OnlineProxy OnlineProxy OnlineProxy Follow Dec 19 '25 Engineering a Multi-Capability MCP Server in Python # programming # ai # beginners # tutorial Comments Add Comment 7 min read Building a Production-Ready Portfolio: Phase 0 - Infra, Git Flow, and Project Foundations Sushant Gaurav Sushant Gaurav Sushant Gaurav Follow Dec 19 '25 Building a Production-Ready Portfolio: Phase 0 - Infra, Git Flow, and Project Foundations # programming # webdev # python # react Comments Add Comment 4 min read React State, Immutability, and Why Mutating Stuff Feels Like Hugging Someone Else’s Wife Farhan Khan Farhan Khan Farhan Khan Follow Dec 16 '25 React State, Immutability, and Why Mutating Stuff Feels Like Hugging Someone Else’s Wife # react # javascript # programming # webdev 1 reaction Comments Add Comment 2 min read Android Performance: Những thứ thật sự làm app chậm (và cách xử lý thực tế) ViO Tech ViO Tech ViO Tech Follow Dec 16 '25 Android Performance: Những thứ thật sự làm app chậm (và cách xử lý thực tế) # android # viodicode # programming # kotlin 5 reactions Comments 2 comments 2 min read Why I Went Back to Basics: What 20,000 XP on W3Schools Taught Me About Coding Sandip Yadav Sandip Yadav Sandip Yadav Follow Jan 9 Why I Went Back to Basics: What 20,000 XP on W3Schools Taught Me About Coding # w3schools # programming # webdev # javascript Comments Add Comment 2 min read Day 9: When Streaks Break and Ambition Returns Blink Blink Blink Follow Dec 15 '25 Day 9: When Streaks Break and Ambition Returns # programming # ai # beginners # productivity 5 reactions Comments Add Comment 2 min read GitHub Copilot Code Review Alternatives: What Works Better? Cubic Cubic Cubic Follow Dec 17 '25 GitHub Copilot Code Review Alternatives: What Works Better? # webdev # ai # programming # productivity Comments Add Comment 4 min read Applying OOP Principles to AI Prompts: Inside the CRAFT Framework Architecture Richard Ketelsen Richard Ketelsen Richard Ketelsen Follow Dec 15 '25 Applying OOP Principles to AI Prompts: Inside the CRAFT Framework Architecture # ai # productivity # programming # architecture Comments Add Comment 2 min read How to improve banking efficiency with custom software? Alex Alex Alex Follow Dec 15 '25 How to improve banking efficiency with custom software? # customsoftware # programming # ai # banking 6 reactions Comments Add Comment 4 min read Integrating AI into a SaaS Platform Coleton Moon Coleton Moon Coleton Moon Follow Dec 15 '25 Integrating AI into a SaaS Platform # programming # ai # webdev # productivity Comments Add Comment 3 min read How SQLite Replaced PostgreSQL as My First Choice Wolfgang Rathgeb Wolfgang Rathgeb Wolfgang Rathgeb Follow Dec 15 '25 How SQLite Replaced PostgreSQL as My First Choice # sql # database # programming Comments Add Comment 4 min read 3562. Maximum Profit from Trading Stocks with Discounts MD ARIFUL HAQUE MD ARIFUL HAQUE MD ARIFUL HAQUE Follow Dec 16 '25 3562. Maximum Profit from Trading Stocks with Discounts # php # leetcode # algorithms # programming Comments Add Comment 13 min read From “I should check the reviews” to a SaaS Quentin Dommerc Quentin Dommerc Quentin Dommerc Follow Dec 15 '25 From “I should check the reviews” to a SaaS # mobile # programming 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:49:04 |
https://docs.python.org/3/library/stdtypes.html#list.append | 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:49:04 |
https://peps.python.org/topic/release/ | Release PEPs | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » Release PEPs Toggle light / dark / auto colour theme Release PEPs Introduction This is the index of all Python Enhancement Proposals (PEPs) labelled under the ‘Release’ topic. This is a sub-index of PEP 0 , the PEP index. A PEP is written to specify the release cycle for each feature release of Python. See the developer’s guide for more information. Index by Category Other Informational PEPs PEP Title Authors IA 619 Python 3.10 Release Schedule Pablo Galindo Salgado 3.10 IA 664 Python 3.11 Release Schedule Pablo Galindo Salgado 3.11 IA 693 Python 3.12 Release Schedule Thomas Wouters 3.12 IA 719 Python 3.13 Release Schedule Thomas Wouters 3.13 IA 745 Python 3.14 Release Schedule Hugo van Kemenade 3.14 IA 790 Python 3.15 Release Schedule Hugo van Kemenade 3.15 Accepted PEPs (accepted; may not be implemented yet) PEP Title Authors SA 773 A Python Installation Manager for Windows Steve Dower Historical Meta-PEPs and Informational PEPs PEP Title Authors IF 160 Python 1.6 Release Schedule Fred L. Drake, Jr. 1.6 IF 200 Python 2.0 Release Schedule Jeremy Hylton 2.0 IF 226 Python 2.1 Release Schedule Jeremy Hylton 2.1 IF 251 Python 2.2 Release Schedule Barry Warsaw, Guido van Rossum 2.2 IF 283 Python 2.3 Release Schedule Guido van Rossum 2.3 IF 320 Python 2.4 Release Schedule Barry Warsaw, Raymond Hettinger, Anthony Baxter 2.4 IF 356 Python 2.5 Release Schedule Neal Norwitz, Guido van Rossum, Anthony Baxter 2.5 IF 361 Python 2.6 and 3.0 Release Schedule Neal Norwitz, Barry Warsaw 2.6, 3.0 IF 373 Python 2.7 Release Schedule Benjamin Peterson 2.7 IF 375 Python 3.1 Release Schedule Benjamin Peterson 3.1 IF 392 Python 3.2 Release Schedule Georg Brandl 3.2 IF 398 Python 3.3 Release Schedule Georg Brandl 3.3 IF 404 Python 2.8 Un-release Schedule Barry Warsaw 2.8 IF 429 Python 3.4 Release Schedule Larry Hastings 3.4 IF 478 Python 3.5 Release Schedule Larry Hastings 3.5 IF 494 Python 3.6 Release Schedule Ned Deily 3.6 IF 537 Python 3.7 Release Schedule Ned Deily 3.7 IF 569 Python 3.8 Release Schedule Łukasz Langa 3.8 IF 596 Python 3.9 Release Schedule Łukasz Langa 3.9 PEP Types Key I — Informational : Non-normative PEP containing background, guidelines or other information relevant to the Python ecosystem P — Process : Normative PEP describing or proposing a change to a Python community process, workflow or governance S — Standards Track : Normative PEP with a new feature for Python, implementation change for CPython or interoperability standard for the ecosystem More info in PEP 1 . PEP Status Key A — Accepted : Normative proposal accepted for implementation A — Active : Currently valid informational guidance, or an in-use process D — Deferred : Inactive draft that may be taken up again at a later time <No letter> — Draft : Proposal under active discussion and revision F — Final : Accepted and implementation complete, or no longer active P — Provisional : Provisionally accepted but additional feedback needed R — Rejected : Formally declined and will not be accepted S — Superseded : Replaced by another succeeding PEP W — Withdrawn : Removed from consideration by sponsor or authors More info in PEP 1 . Contents Index by Category Other Informational PEPs Accepted PEPs (accepted; may not be implemented yet) Historical Meta-PEPs and Informational PEPs PEP Types Key PEP Status Key | 2026-01-13T08:49:04 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fkeefdrive%2Fcreate-react-app-vs-vite-2amn&title=Create%20react%20app%20vs%20Vite&summary=I%20have%20always%20relied%20on%20the%20npm%20command%20create-react-app%20to%20create%20the%20starter%20files%20for%20any%20React.js...&source=DEV%20Community | LinkedIn {"data":{"status":401},"included":[]} {"request":"/voyager/api/voyagerSegmentsDashChameleonConfig","status":401,"body":"bpr-guid-597395","method":"GET","headers":{"x-li-uuid":"AAZIQRA0CuqMjP/UZRbgAA\u003D\u003D"}} {"data":{"status":401},"included":[]} {"request":"/voyager/api/voyagerLaunchpadDashLaunchpadViews?decorationId\u003Dcom.linkedin.voyager.dash.deco.launchpad.LaunchpadView-96\u0026launchpadContext\u003DTAKEOVER\u0026q\u003Dcontext","status":401,"body":"bpr-guid-597396","method":"GET","headers":{"x-li-uuid":"AAZIQRA0CuqMjP/UZRbgAA\u003D\u003D"}} {"data":{"status":401},"included":[]} {"request":"/voyager/api/me","status":401,"body":"bpr-guid-597397","method":"GET","headers":{"x-li-uuid":"AAZIQRA0CuqMjP/UZRbgAA\u003D\u003D"}} {"data":{"status":401},"included":[]} {"request":"/voyager/api/premium/featureAccess?name\u003DreactivationFeaturesEligible","status":401,"body":"bpr-guid-597398","method":"GET","headers":{"x-li-uuid":"AAZIQRA0CuqMjP/UZRbgAA\u003D\u003D"}} urn:li:page:d_UNKNOWN_ROUTE_inshare-redirect;96677432-4783-45d1-b9a3-69b5c3700afe | 2026-01-13T08:49:04 |
https://tatanotes.com/blog/accessibility-testing-on-windows-on-mac/ | TataNotes – Web Accessibility Personal Blog Accessibility Testing on Windows on Mac – TataNotes Skip to main content TataNotes… …all about a11y Blog About me Tutorials Accessibility Testing on Windows on Mac A quick guide to Accessibility Testing using Windows-only tools on a modern Mac with Apple Silicon processor. Reading time: around 3 min Publication date May 12, 2025 Today’s note is about something that I, as a new Mac user, had to deal with while setting up my work environment. TL;DR: To run NVDA Opens a new page and JAWS Opens a new page on a Mac, you need to install Windows 11 for ARM Opens a new page in a virtual machine like UTM Opens a new page , and map a spare key to the Insert key with SharpKeys Opens a new page . Why do accessibility testing on Windows if you have a Mac? According to the WebAIM Screen Reader User Survey #10 Opens a new page , Windows-only screen readers NVDA and JAWS are used by the majority of users. Just like browsers, screen readers have differences in how they present information, so it’s always a good idea to test your website or app using different browser/screen reader combinations. In addition, some of the styling, like box shadows, background images, and so on, is removed when Windows High Contrast Mode (WHCM) is enabled. Sadly, there is no alternative to the WHCM on the Mac. Installation Step 1 – Installing a virtual machine There are multiple virtual machines available on Mac, such as Parallels, VirtualBox, and UTM. I’m using UTM, but this guide doesn’t depend on its specifics, so you can choose whatever works for you. You can download UTM for free from the official website Opens a new page . You can also purchase it from the Mac App Store Opens a new page to support the team behind the software. Step 2 – Installing Windows When you have got UTM up and running, create a new virtual machine. You will need a Windows installation disk image, which you can download from the Microsoft website Opens a new page . Click on “Create a New Virtual Machine”, select “Virtualize”, and follow the wizard. You will need to specify the path to the installation ISO here. Step 3 – Installing screen readers Both NVDA Opens a new page and JAWS Opens a new page work on ARM-based devices now, so you can install them in a virtual machine, just as you would on a real device. If you would like to install any other programs, make sure that they also support ARM processors. Step 4 – Mapping missing keys Due to the fact that Mac and Windows use different keyboards, you are not able to use the Insert key in your UTM virtual machine. (You will need it for the various shortcuts for NVDA and JAWS.) You have to use a third-party program to remap keys on Mac or Windows level. I’m using SharpKeys Opens a new page – an open-source program for Windows. Download, install, and run SharpKeys inside the virtual machine . Click on the “Add” button. In the new window, find “Special: Insert” on the right. In the left list, select a key that you would like to act as the Insert key. For instance, if you select F1 on the left, every time you press F1 key inside your virtual machine, it will register as Insert. Make sure to map a key that is not used in any shortcuts. Once finished, press “OK”, and then “Write to registry” to save changes – it will not work otherwise. At this point, you’re good to go and start your accessibility testing. Hooray! Step 5 (bonus) – Accessing localhost If you are developing a project and running it locally, you might want to do quality assurance before deploying changes. For this, you need to be able to access your project at http://localhost:port from within the virtual machine. One way to do that with UTM is to set the network mode for the virtual machine to “Shared Network”. Then, look up the Default Gateway IP address in Windows, which you can do by running ipconfig command in the Command Prompt: Now make sure that your project is accepting requests to this IP address. For example, to run a SvelteKit project in development mode and accept connections on all available IP addresses, you need to slightly modify the default command: npm run dev -- --host You can find a similar command for your tool. Extensive accessibility testing is important Mac is a great platform for web development. However, the reality is that majority of desktop users are Windows users. Thanks to tools like UTM, we are able to run Windows and Windows-specific software directly on a Mac. By testing on a wide range of tools and platforms, we make the Web accessible for all. Tatyana Bayramova © 2024–present Important: All rights reserved | 2026-01-13T08:49:04 |
https://wiki.python.org/psf/ConductWG/Charter | ConductWG/Charter - PSF Wiki Search: ConductWG Charter FrontPage Contents RecentChanges FindPage HelpContents ConductWG/Charter Page Immutable Page Comments Info Attachments More Actions: Raw Text Print View Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ ------------------------ Remove Spam Revert to this revision ------------------------ SlideShow User Login PSF Code of Conduct Workgroup Charter Contents PSF Code of Conduct Workgroup Charter Purpose & Common Goals Active Time Core Values Membership Rules & Guidelines Decision Making Procedures Communication Plan Budget List of Participants/Who we are Purpose & Common Goals The workgroup's purpose is to foster a diverse and inclusive Python community by enforcing the PSF code of conduct, along with providing guidance and recommendations to the Python community on codes of conduct, that supports the PSF mission of “ongoing development of Python-related technology and educational resources”. We work toward this common goal in three ways: Review, revise, and advise on policies relating to the PSF code of conducts and other communities that the PSF supports. This includes any #python chat community & python.org email list under PSF jurisdiction. Create a standard set of codes of conduct and supporting documents for multiple channels of interaction such as, but not limited to, conferences, mailing lists, slack/IRC, code repositories, and more. Develop training materials and other processes to support Python community organizers in implementing and enforcing the code of conduct. Active Time It will continue to exist as long as the workgroup and the PSF Board determines it is needed. Core Values The core values for this group are: Respect Support Constructiveness Integrity The workgroup adopts the PSF Code of Conduct ( https://www.python.org/psf/codeofconduct/ ). Any actions made against the principles in the Code of Conduct (found by a simple majority of 51%+) will result in the acting person being removed from the workgroup. Membership Code of Conduct Workgroup voting members are required to confirm continuing participating in the workgroup within one month of a new board election. This will be led by chair/vice-chairs. If there is no response within two weeks, then the individual is automatically removed. A member of the Code of Conduct Workgroup, can step down at anytime, and the workgroup will work to replace that voting member. If a member fails to attend more than 50% of meetings over a 3-month span (4 out of 6 meetings), they will be moved to the Past Members list unless they make arrangements with the Workgroup in advance. They are welcome to rejoin at any time. Folks that would like to join the Code of Conduct Work Group should send an email to the WG ( conduct-wg@python.org ) introducing themselves. The WG will vote on new member requests verbally at their every meeting. Rules & Guidelines * "The Code of Conduct Workgroup will strive to include and understand a diverse group of perspectives as it implements its mission The workgroup reserves the right to consult with outside experts. The Code of Conduct Workgroup will submit a monthly report to the PSF board of directors. Decision Making Procedures Discussions will happen via phone, video chat, or mailing list. With respect to new code of conduct standards and policy recommendations: The workgroup may solicit feedback on proposed drafts. The workgroup will consider outside input, edit the document, then vote for final approval. The workgroup will vote on new standards and will require half of all voting members plus one to be present for quorum and new motions will require approval of half of all voting members plus one. Communication Plan The team will communicate via the conduct-wg@python.org mailing list. If needed, conference calls may be set up. The method of voting on projects and proposals will be determined by the workgroup. Preferred method of voting will be electronically (email or chat) and the vote results will be reported via email to the board in the monthly report. We will attempt to limit information shared about specific instances. Our priority is ensuring community members' safety, but we protect individuals' privacy to the greatest extent possible. Calls and face-to-face meetings are preferred for discussions of specific incidence. Budget $5,000 List of Participants/Who we are Chairs: Tania Allard and Jessica Greene Participants: Tania Allard KwonHan Bae Brett Cannon Rami Chowdhury Jessica Greene Cheuk Ting Ho Jeremy Hylton Deb Nicholson Monica Oyugi Mojdeh Rastgoo Jeff Triplett Koti Vellanki Drew Winstel Past members: Joe Banks Naomi Ceder (non-voting) Anwesha Das Trey Hunner Philip James Ewa Jodlowska (non-voting) Jackie Kazil Van Lindberg Lorena Mesa Maricela Sanchez Miranda Kenneth Reitz Sasha Romijn Reshama Shaikh Carol Willing Thomas Wouters (non-voting) Mercedes Wyss Tereza Iofciu Łukasz Langa ConductWG/Charter (last edited 2025-05-02 13:23:08 by TaniaAllard ) MoinMoin Powered Python Powered GPL licensed Valid HTML 4.01 Unable to view page? See the FrontPage for instructions. | 2026-01-13T08:49:04 |
https://dev.to/t/tutorial/page/4#main-content | Tutorial Page 4 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # tutorial Follow Hide Tutorial is a general purpose tag. We welcome all types of tutorial - code related or not! It's all about learning, and using tutorials to teach others! Create Post submission guidelines Tutorials should teach by example. This can include an interactive component or steps the reader can follow to understand. Older #tutorial posts 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 Golang: Trying out Go Proposal 45713 'Multi-Module Workspaces' Evan Lin Evan Lin Evan Lin Follow Jan 11 Golang: Trying out Go Proposal 45713 'Multi-Module Workspaces' # go # tooling # tutorial Comments Add Comment 2 min read [TIL] Deploying to Heroku with Github Releases and Golang Evan Lin Evan Lin Evan Lin Follow Jan 11 [TIL] Deploying to Heroku with Github Releases and Golang # cicd # github # tutorial # go Comments Add Comment 2 min read Learning Golang REGEX with ChatGPT Evan Lin Evan Lin Evan Lin Follow Jan 11 Learning Golang REGEX with ChatGPT # learning # chatgpt # go # tutorial Comments Add Comment 2 min read 🕰️ Building a Modern Alarm Clock App in Python with Tkinter Mate Technologies Mate Technologies Mate Technologies Follow Jan 11 🕰️ Building a Modern Alarm Clock App in Python with Tkinter # python # opensource # alarmclock # tutorial Comments Add Comment 4 min read [Google Colab][Python] How to Upgrade Python 3.9 to 3.11 Evan Lin Evan Lin Evan Lin Follow Jan 11 [Google Colab][Python] How to Upgrade Python 3.9 to 3.11 # google # python # tutorial Comments Add Comment 2 min read [Golang][Render] Deploying a Golang App to Render.com with GitHub Actions Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang][Render] Deploying a Golang App to Render.com with GitHub Actions # cicd # github # go # tutorial Comments Add Comment 2 min read [Golang][Notion] How to Use Golang to Control a Notion DB as an Online Database Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang][Notion] How to Use Golang to Control a Notion DB as an Online Database # database # go # api # tutorial Comments Add Comment 5 min read Gemini/Firebase: Building a Tech News LINE Bot with IFTTT and LangChain Evan Lin Evan Lin Evan Lin Follow Jan 11 Gemini/Firebase: Building a Tech News LINE Bot with IFTTT and LangChain # gemini # automation # llm # tutorial Comments Add Comment 1 min read Creating Spotlight Tutorials in Flutter: The Complete Guide to Selective Overlays Thanasis Traitsis Thanasis Traitsis Thanasis Traitsis Follow Jan 11 Creating Spotlight Tutorials in Flutter: The Complete Guide to Selective Overlays # flutter # dart # tutorial # coding Comments Add Comment 12 min read My Ray-Ban Meta Glasses AI Setup in Taiwan Evan Lin Evan Lin Evan Lin Follow Jan 11 My Ray-Ban Meta Glasses AI Setup in Taiwan # ai # iot # tutorial Comments Add Comment 2 min read Installing Arch Linux in 2026 (step-by-step) ZionS1_1 ZionS1_1 ZionS1_1 Follow Jan 11 Installing Arch Linux in 2026 (step-by-step) # bash # archlinux # linux # tutorial Comments Add Comment 5 min read How to Generate Test Data for PostgreSQL (2 Methods) DDLTODATA DDLTODATA DDLTODATA Follow Jan 11 How to Generate Test Data for PostgreSQL (2 Methods) # postgres # testing # data # tutorial Comments Add Comment 3 min read [n8n][Gemini] Building an AI-Powered RSS Summary System with Daily LINE Notifications Evan Lin Evan Lin Evan Lin Follow Jan 11 [n8n][Gemini] Building an AI-Powered RSS Summary System with Daily LINE Notifications # gemini # automation # productivity # tutorial 1 reaction Comments Add Comment 5 min read [TIL] A Three-Hour Interview with Ji Yichao, Chief Scientist at Manus (Acquired by Meta) Evan Lin Evan Lin Evan Lin Follow Jan 11 [TIL] A Three-Hour Interview with Ji Yichao, Chief Scientist at Manus (Acquired by Meta) # programming # devops # tutorial Comments Add Comment 4 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 Adeus, Swagger UI ? Uma alternativa elegante com Redoc Danilo O. Pinheiro, dopme.io Danilo O. Pinheiro, dopme.io Danilo O. Pinheiro, dopme.io Follow Jan 10 Adeus, Swagger UI ? Uma alternativa elegante com Redoc # dotnet # csharp # api # tutorial Comments Add Comment 7 min read Cloud Computing - Virtual Private Cloud (VPC) Setup - Complete Tutorial Hemanath Kumar J Hemanath Kumar J Hemanath Kumar J Follow Jan 11 Cloud Computing - Virtual Private Cloud (VPC) Setup - Complete Tutorial # tutorial # cloud # aws # vpc Comments Add Comment 2 min read Rails 8 Strong Parameters: The Double-Bracket Fix for Nested Attributes Olumuyiwa Osiname Olumuyiwa Osiname Olumuyiwa Osiname Follow Jan 11 Rails 8 Strong Parameters: The Double-Bracket Fix for Nested Attributes # tutorial # backend # rails # ruby Comments Add Comment 3 min read Setting Up Your Own Linux Server with Hetzner: A Technical Guide ITpraktika.com ITpraktika.com ITpraktika.com Follow Jan 11 Setting Up Your Own Linux Server with Hetzner: A Technical Guide # linux # devops # serverless # tutorial Comments Add Comment 6 min read Your Proxy Should Only Allow Requests with a Custom Header — How Do You Do It in Apigee X? realNameHidden realNameHidden realNameHidden Follow Jan 11 Your Proxy Should Only Allow Requests with a Custom Header — How Do You Do It in Apigee X? # security # api # tutorial # cloud 5 reactions Comments Add Comment 3 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 How I Built a Real API Gateway Using Cloudflare Workers (And Why It Matters) Shafqat Awan Shafqat Awan Shafqat Awan Follow Jan 11 How I Built a Real API Gateway Using Cloudflare Workers (And Why It Matters) # architecture # api # tutorial # serverless Comments Add Comment 2 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 Polyfill - useEffect (React) ZeeshanAli-0704 ZeeshanAli-0704 ZeeshanAli-0704 Follow Jan 11 Polyfill - useEffect (React) # javascript # react # tutorial Comments Add Comment 5 min read Polyfil - useReducer ZeeshanAli-0704 ZeeshanAli-0704 ZeeshanAli-0704 Follow Jan 11 Polyfil - useReducer # interview # tutorial # javascript # react Comments Add Comment 5 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/t/programming/page/73 | Programming Page 73 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 70 71 72 73 74 75 76 77 78 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 8 Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 # go # linux # opensource # programming 5 reactions Comments Add Comment 5 min read Start, Stop, and Continue for 2026 Aaron McCollum Aaron McCollum Aaron McCollum Follow Dec 19 '25 Start, Stop, and Continue for 2026 # webdev # programming # learning Comments Add Comment 3 min read Amazon S3 Explained: Simple Storage in the Cloud MATHAN S MATHAN S MATHAN S Follow Dec 18 '25 Amazon S3 Explained: Simple Storage in the Cloud # cloud # devops # aws # programming Comments Add Comment 1 min read MURAL: A Visual Collaboration Tool in the DevSecOps Periodic Table MATHAN S MATHAN S MATHAN S Follow Dec 18 '25 MURAL: A Visual Collaboration Tool in the DevSecOps Periodic Table # devops # mural # programming # opensource Comments Add Comment 1 min read Leetcode 39 Combination Sum Wincy H Wincy H Wincy H Follow Dec 17 '25 Leetcode 39 Combination Sum # leetcode # programming # python # tutorial Comments Add Comment 3 min read Torrance Motors: Building a Fast, Reliable Automotive Website with C++ — Challenges Faced and Future Goals Alfie John Alfie John Alfie John Follow Dec 18 '25 Torrance Motors: Building a Fast, Reliable Automotive Website with C++ — Challenges Faced and Future Goals # webdev # programming # ai # javascript Comments Add Comment 9 min read A Better Way to Run Git Worktrees Finally! Julio Daniel Reyes Julio Daniel Reyes Julio Daniel Reyes Follow Dec 16 '25 A Better Way to Run Git Worktrees Finally! # git # vibecoding # programming # ai 27 reactions Comments Add Comment 1 min read How We Actually Ship Complex Systems with AI Agents Ali Baqbani Ali Baqbani Ali Baqbani Follow Dec 18 '25 How We Actually Ship Complex Systems with AI Agents # ai # programming # softwaredevelopment # architecture Comments Add Comment 3 min read Productionizing Model Context Protocol Servers OnlineProxy OnlineProxy OnlineProxy Follow Dec 17 '25 Productionizing Model Context Protocol Servers # programming # ai # beginners # tutorial Comments Add Comment 7 min read 🚀 Launching Vyoma Labs: A Research-First Space for Building the Future of the Web Prasoon Jadon Prasoon Jadon Prasoon Jadon Follow Dec 17 '25 🚀 Launching Vyoma Labs: A Research-First Space for Building the Future of the Web # webdev # programming # startup # opensource Comments Add Comment 3 min read Vibe Coding hit a wall: How I fixed $0.30/error OOMs and cut AI costs by 70% renming wang renming wang renming wang Follow Dec 17 '25 Vibe Coding hit a wall: How I fixed $0.30/error OOMs and cut AI costs by 70% # webdev # ai # programming # productivity 1 reaction Comments 1 comment 2 min read Introducing temporal-contract: Type-Safe Temporal. io Workflows for TypeScript Benoit Travers Benoit Travers Benoit Travers Follow Dec 21 '25 Introducing temporal-contract: Type-Safe Temporal. io Workflows for TypeScript # typescript # node # programming # productivity 2 reactions Comments Add Comment 8 min read AWS CodeDeploy: A Beginner-Friendly Guide to Automated Deployments Ege Pakten Ege Pakten Ege Pakten Follow Dec 17 '25 AWS CodeDeploy: A Beginner-Friendly Guide to Automated Deployments # aws # codedeploy # programming # infrastructureascode Comments Add Comment 5 min read The New Field Keyword Improves Properties in C# 14 Adrián Bailador Adrián Bailador Adrián Bailador Follow Dec 17 '25 The New Field Keyword Improves Properties in C# 14 # csharp # dotnet # programming # webdev Comments Add Comment 6 min read Atlassian Bamboo in the DevSecOps Periodic Table ABITHA N 24CB001 ABITHA N 24CB001 ABITHA N 24CB001 Follow Dec 18 '25 Atlassian Bamboo in the DevSecOps Periodic Table # devops # devsecops # programming # learning Comments Add Comment 1 min read I Built a Clean Age Calculator Because Most of Them Get the Details Wrong Momin Ali Momin Ali Momin Ali Follow Dec 18 '25 I Built a Clean Age Calculator Because Most of Them Get the Details Wrong # programming # webdev # javascript 1 reaction Comments 1 comment 2 min read StableJSON: A Practical Workspace for Serious JSON Work Debjit Dey Debjit Dey Debjit Dey Follow Dec 31 '25 StableJSON: A Practical Workspace for Serious JSON Work # programming # webdev # devtool # json Comments 1 comment 2 min read How One Can Start Their Journey in Data Engineering Chetan Gupta Chetan Gupta Chetan Gupta Follow Jan 10 How One Can Start Their Journey in Data Engineering # programming # dataengineering # sql # beginners Comments 2 comments 4 min read AI-Powered Programming: Creating My Own Magical Flashcards Study App Daniel Daniel Daniel Follow for Datalaria Jan 10 AI-Powered Programming: Creating My Own Magical Flashcards Study App # showdev # ai # programming 5 reactions Comments 2 comments 5 min read Beyond the Screen: Why LLMs Don't Need Browsers (And Why We Think They Do) Edward Burton Edward Burton Edward Burton Follow Dec 17 '25 Beyond the Screen: Why LLMs Don't Need Browsers (And Why We Think They Do) # webdev # programming # ai # browser 1 reaction Comments Add Comment 8 min read YAML Formatter Pineapple Pineapple Pineapple Follow Dec 22 '25 YAML Formatter # webdev # programming # beginners # kubernetes Comments Add Comment 2 min read Day 73: Python Longest Palindromic Substring – Expand-Around-Center O(n^2) Technique for Max Palindrome (LeetCode #5 Guide) Shahrouz Nikseresht Shahrouz Nikseresht Shahrouz Nikseresht Follow Dec 23 '25 Day 73: Python Longest Palindromic Substring – Expand-Around-Center O(n^2) Technique for Max Palindrome (LeetCode #5 Guide) # challenge # python # algorithms # programming Comments Add Comment 2 min read The Time Our Pipeline Processed the Same Day’s Data 47 Times Pradeep Kalluri Pradeep Kalluri Pradeep Kalluri Follow Dec 17 '25 The Time Our Pipeline Processed the Same Day’s Data 47 Times # dataengineering # airflow # python # programming Comments Add Comment 5 min read How I Use AI to Build Full-Stack Apps (The Pipeline Nobody Talks About) Edjere Evelyn Oghenetejiri Edjere Evelyn Oghenetejiri Edjere Evelyn Oghenetejiri Follow Dec 17 '25 How I Use AI to Build Full-Stack Apps (The Pipeline Nobody Talks About) # webdev # ai # programming # nextjs 1 reaction Comments Add Comment 3 min read I Built a Deterministic Life Tool (and Intentionally Removed “AI” From the Loop) FlameAI Studio FlameAI Studio FlameAI Studio Follow Dec 17 '25 I Built a Deterministic Life Tool (and Intentionally Removed “AI” From the Loop) # webdev # programming # productivity # beginners Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://tatanotes.com/blog/international-day-of-persons-with-disabilities-2024 | TataNotes – Web Accessibility Personal Blog International Day of Persons with Disabilities – TataNotes Skip to main content TataNotes… …all about a11y Blog About me Raising Awareness International Day of Persons with Disabilities Today we raise awareness on issues that people with disabilities deal with on a daily basis. Reading time: around 2 min Publication date December 3, 2024 Today, December 3rd, is the International Day of Persons with Disabilities. The United Nations General Assembly proclaimed the annual observance of this day in October 1992 ( resolution 47/3 ). Each year, this day is observed with a focus on a specific theme. The 2024 theme is Amplifying the leadership of persons with disabilities for an inclusive and sustainable future . Disability impacts more people than you might think It is estimated that 1 in 4 adults in the European Union have at least one disability ( Eurostat ). In the United States, the number is even higher — 28.7% of the adult population are people with disabilities ( CDC ). Overall, 1.3 billion people around the globe would benefit from accessible solutions ( WHO ). With aging population we can only expect a rise in numbers in the future ( Eurostat ). Contributing towards the accessible future There are many ways to improve quality of live for people with disabilities. For example, cities could invest more in accessible infrastructure, such as wheelchair ramps, elevators, or tactile pavings. Another way is to promote use of assistive technologies, like screen readers, screen magnifiers, or braille displays. 💡 Did you know? Everyday things like eyeglasses or walking sticks are also considered assistive technology. As more and more services go online, it’s more important than ever for software to have an accessible user interface. Web Content Accessibility Guidelines ( WCAG ) help developers to create web pages and web applications that are easy to use, navigate, and understand. Enhanced accessibility is not only beneficial for people with disabilities. For example, ramps designed for wheelchair users are also helpful for people with strollers; a website with keyboard navigation support is easy to use for people with a temporary impairment as well (e.g., a broken arm). Accessibility is a necessity, not a premium We all can make a contribution towards a more accessible world. By promoting and implementing inclusive ideas, we make sure that each and every member of society is able to live their life to the fullest. We need to remember: accessibility is not a premium feature, but a necessity for a functioning society . To understand the extent of the need for an inclusive world, I invite you to watch the video below, which shows a world where the roles are reversed. Transcript Imagine a town full of physically impaired people, all wheelchair users. They run everything. There aren't any able-bodied people, so, naturally, when they built the town, the community decided it was pointless to have ceilings 10-foot high and doors 7-foot high, so the ceilings were built at 7 foot the doors at 5 foot. In every way, they designed the place the way they wanted it. One day, a few able-bodied people come to stay. One of the first things they notice is the height of the doors. And the reason they notice is because they keep hitting their heads. They come to stand out by the bruises they carry on their foreheads. Soon, doctors, psychiatrists, and social workers all become involved. Committees are formed. Many people are worried about what becomes known as “the problem of the able-bodied.” Throughout the town there is a growth of real concern. Specially toughened helmets are handed out free to the able-bodied, to be worn at all times. Braces are designed, which give support and relief while keeping the able-bodied wearer bent to normal height. Various groups of compassionate wheelchair users get together and form registered charities. Every quarter, they have a collection day. Upturned helmets are left in pubs and shops for people to drop their small change into. There is talk of founding special homes. But then, one day, it dawns on the able-bodied that there is nothing actually wrong with them, just that society excludes them. Tatyana Bayramova © 2024–present Important: All rights reserved | 2026-01-13T08:49:04 |
https://dev.to/sagarparmarr/genx-from-childhood-flipbooks-to-premium-scroll-animation-1j4#comments | GenX: From Childhood Flipbooks to Premium Scroll Animation - 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 Sagar Posted on Jan 13 • Originally published at sagarparmarr.hashnode.dev GenX: From Childhood Flipbooks to Premium Scroll Animation # webdev # performance # animation Build buttery-smooth, Apple-style image sequence animations on canvas + the tiny redraw hack that saves up to 80% GPU/battery power Hey there, fellow web dev enthusiasts! 🖐️ Remember those childhood flipbooks where you'd scribble a stick figure on the corner of your notebook pages, flip through them furiously, and suddenly – bam – your doodle was dancing? That's the nostalgic spark behind one of the coolest tricks in modern web design: image sequence animations . You've seen them on slick landing pages – those buttery-smooth, scroll-driven "videos" that feel alive as you navigate the site. But here's the plot twist: they're not videos at all . They're just a clever stack of images, orchestrated like a symphony on a <canvas> element. In this post, we're diving into how these animations work, why they're a game-changer for interactive storytelling, and – drumroll please 🥁 – a tiny optimization that stops your user's device from chugging power like it's training for a marathon. Let's flip the page and get started! ✨ Classic flipbook magic – the inspiration behind modern web wizardry Quick access (want to play right away?) → Live Demo → Full source code on GitHub Now let's get into how this magic actually works... Chapter 1: The Flipbook Reborn – What Is Image Sequence Animation? Picture this: You're on a high-end e-commerce site, scrolling down a product page. As your finger glides, a 3D model spins seamlessly, or a background scene morphs from day to night. It looks like high-def video, but peek at the network tab – no MP4 in sight . Instead, it's a barrage of optimized images (usually 100–200 WebP files) doing the heavy lifting. At its core, image sequence animation is digital flipbook wizardry : Export a video/animation as individual frames Preload them into memory as HTMLImageElement objects Drive playback with scroll position (0% = frame 1, 100% = last frame) Render the right frame on <canvas> Why choose this over <video> ? 🎮 Total control — perfect sync with scroll, hover, etc. ⚡ Lightweight hosting — images cache beautifully on CDNs, compress with WebP/AVIF 😅 No encoding drama — skip codecs, bitrates, and cross-browser video nightmares But every hero has a weakness: lots of network requests + heavy repainting = GPU sweat & battery drain on big/retina screens. We'll fix that soon. Smooth scroll-triggered image sequence in action Chapter 2: Behind the Curtain – How the Magic Happens (With Code!) Here's the typical flow in a React-ish world (pseudocode – adapt to vanilla/Vue/Svelte/whatever you love): // React-style pseudocode – hook it up to your scroll listener! const FRAME_COUNT = 192 ; // Your total frames const targetFrameRef = useRef ( 0 ); // Scroll-driven goal const currentFrameRef = useRef ( 0 ); // Current position const rafRef = useRef < number | null > ( null ); // Update target on scroll (progress: 0-1) function onScrollChange ( progress : number ) { const nextTarget = Math . round ( progress * ( FRAME_COUNT - 1 )); targetFrameRef . current = Math . clamp ( nextTarget , 0 , FRAME_COUNT - 1 ); // Assuming a clamp util } // The animation loop: Lerp and draw useEffect (() => { const tick = () => { const curr = currentFrameRef . current ; const target = targetFrameRef . current ; const diff = target - curr ; const step = Math . abs ( diff ) < 0.001 ? 0 : diff * 0.2 ; // Close the gap by 20% each frame const next = step === 0 ? target : curr + step ; currentFrameRef . current = next ; drawFrame ( Math . round ( next )); // Render the frame rafRef . current = requestAnimationFrame ( tick ); }; rafRef . current = requestAnimationFrame ( tick ); return () => { if ( rafRef . current ) cancelAnimationFrame ( rafRef . current ); }; }, []); function drawFrame ( index : number ) { const ctx = canvasRef . current ?. getContext ( ' 2d ' ); if ( ! ctx ) return ; // Clear, fill background, and draw image with contain-fit const img = preloadedImages [ index ]; ctx . clearRect ( 0 , 0 , canvas . width , canvas . height ); // ...aspect ratio calculations and drawImage() here... } Enter fullscreen mode Exit fullscreen mode Elegant, right? But here's the villain... The Plot Twist: Idle Repaints = Battery Vampires 🧛♂️ When users pause to read copy or admire the product, that requestAnimationFrame loop keeps churning 60 times per second … redrawing the exact same frame over and over. On high-DPI/4K retina screens? → Massive canvas clears → Repeated image scaling & smoothing → Constant GPU compositing The result: laptop fans kick into overdrive, the device heats up, and battery life tanks fast. I've seen (and measured) this in real projects — idle GPU/CPU spikes that turn a "premium" experience into a power hog. Time for the hero upgrade! Here are real before/after screenshots from my own testing using Chrome DevTools with Frame Rendering Stats enabled (GPU memory + frame rate overlay visible): Before: ~15.6 MB GPU idle After: ~2.4 MB GPU idle Before Optimization After Optimization Idle state with constant repaints – 15.6 MB GPU memory used Idle state post-hack – only 2.4 MB GPU memory used See the difference? Before : ~15.6 MB GPU memory in idle → heavy, wasteful repainting After : ~2.4 MB GPU memory → zen-like efficiency This tiny check eliminates redundant drawImage() calls and can drop idle GPU usage by up to 80% in heavy canvas scenarios (your mileage may vary based on resolution, DPR, and image size). Pro tip: Enable Paint flashing (green highlights) + Frame Rendering Stats in DevTools → scroll a bit, then pause. Watch the green flashes disappear and GPU stats stabilize after applying the fix. Battery saved = happier users + longer sessions 🌍⚡ Chapter 3: The Hero's Hack – Redraw Only When It Matters Super simple fix: track the last drawn frame index and skip drawImage() if nothing changed. useEffect (() => { let prevFrameIndex = Math . round ( currentFrameRef . current ); const tick = () => { // ... same lerp logic ... currentFrameRef . current = next ; const nextFrameIndex = Math . round ( next ); // ★ The magic line ★ if ( nextFrameIndex !== prevFrameIndex ) { drawFrame ( nextFrameIndex ); prevFrameIndex = nextFrameIndex ; } rafRef . current = requestAnimationFrame ( tick ); }; rafRef . current = requestAnimationFrame ( tick ); return () => cancelAnimationFrame ( rafRef . current ! ); }, []); Enter fullscreen mode Exit fullscreen mode Why this feels like a superpower Scrolling → still buttery-smooth (draws only when needed) Idle → zen mode (just cheap math, no GPU pain) Real-world wins → up to 80% less idle GPU usage in my tests Pro tip: Use Paint Flashing + Performance tab in DevTools to see the difference yourself. Try it yourself! Here's a minimal, production-ready demo you can fork and play with: → Live Demo → Full source code on GitHub Extra Twists: Level Up Your Animation Game ⚙️ DPR Clamp → cap devicePixelRatio at 2 🖼️ Smart contain-fit drawing (calculate once) 🚀 WebP/AVIF + CDN caching 👀 IntersectionObserver + document.hidden → pause when out of view 🔼 Smart preloading → prioritize first visible frames The Grand Finale: Flipbooks for the Future Image sequence animations are the unsung heroes of immersive web experiences – turning static pages into interactive stories without video baggage . With this tiny redraw check, you're building cool and efficient experiences. Your users (and their batteries) will thank you. Got questions, your own hacks, or want to share a project? Drop them in the comments – let's geek out together! 🚀 Happy coding & happy low-power animating! ⚡ 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 Sagar Follow Joined Mar 28, 2024 Trending on DEV Community Hot Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming What was your win this week??? # weeklyretro # discuss Inside the SQLite Frontend: Tokenizer, Parser, and Code Generator # webdev # programming # database # architecture 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://popcorn.forem.com/_c9af00d5bb7c26378eceb | 채혁기 - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Follow User actions 채혁기 404 bio not found Joined Joined on Dec 4, 2025 More info about @_c9af00d5bb7c26378eceb Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 1 post published Comment 0 comments written Tag 0 tags followed 2025년 기대되는 K-드라마 신작 TOP 5 채혁기 채혁기 채혁기 Follow Dec 5 '25 2025년 기대되는 K-드라마 신작 TOP 5 # kdrama # korean # entertainment # tv 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 Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:04 |
https://zeroday.forem.com/privacy#12-contact-us | Privacy Policy - Security Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Security Forem Close 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 Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:49:04 |
https://ironpython.net/ | IronPython.net / Overview Download Tools Documentation Support Blog IronPython the Python programming language for .NET IronPython is an open-source implementation of the Python programming language which is tightly integrated with .NET. IronPython can use .NET and Python libraries, and other .NET languages can use Python code just as easily. 2.7 2.7.12 released on 2022-01-21 release notes | source 3.4 3.4.2 released on 2024-12-19 release notes | source 3.4 3.4.0-beta1 released on 2022-04-30 release notes | source --> Try Python in the browser Quickly run Python code in your browser, without installing IronPython. --> Experience a more interactive .NET and Python development experience with Python Tools for Visual Studio . Why IronPython? IronPython is an excellent addition to .NET, providing Python developers with the power of the .NET. Existing .NET developers can also use IronPython as a fast and expressive scripting language for embedding, testing, or writing a new application from scratch. The CLR is a great platform for creating programming languages, and the DLR makes it all the better for dynamic languages. Also, the .NET (base class library, presentation foundation, etc.) gives developers an amazing amount of functionality and power. Announcements December 19, 2024 IronPython 3.4.2 is now available! See the release announcement for details. July 12, 2023 IronPython 3.4.1 is now available! See the release announcement for details. December 12, 2022 IronPython 3.4.0 is now available! See the release announcement for details. April 30, 2022 IronPython 3.4.0-beta1 is now available! See the release announcement for details. January 21, 2022 IronPython 2.7.12 is now available! See the release announcement for details. April 19, 2021 IronPython 3.4.0-alpha1 is now available! See the release announcement for details. November 17, 2020 IronPython 2.7.11 is now available! This release resolves issues with .NET 5. See the release announcement for details. April 27, 2020 IronPython 2.7.10 is now available! This release provides .NET Core and .NET Standard support. See the release announcement for details. October 9, 2018 IronPython 2.7.9 is now available! This release includes many fixes. See the release announcement for details. February 16, 2018 IronPython 2.7.8 is now available! This release includes many fixes. See the release announcement for details. December 7, 2016 IronPython 2.7.7 is now available! This release includes many fixes. See the release announcement for details. August 20, 2016 IronPython 2.7.6 is now available! This release includes many fixes. See the release announcement for details. December 6, 2014 IronPython 2.7.5 is now available! This release includes ensurepip and many other fixes. See the release announcement for details. November 21, 2014 IronPython 2.7.5 Release Candidate 1 is now available! See the release announcement for details. May 25, 2014 IronPython 2.7.5 Beta 2 is now available! See the release announcement for details. September 7, 2013 IronPython 2.7.4 is now available! This includes numerous fixes, including several improvements to the ast module and other compatibility fixes. See the release announcement for details. August 17, 2013 IronPython 2.7.4 Release Candidate is now available! July 6, 2012 IronPython 2.7.3 is now available! This release includes support for the bz2, winsound, and _bisect modules, major improvements to the _ast module, improvements in Android support, improvements to pyc.py, and a new console that supports history and tab completion on all platforms. See what's new in 2.7.3 for more information. All IronPython Announcements © .NET Foundation Overview Download Tools Documentation Support Blog | 2026-01-13T08:49:04 |
https://www.python.org/community/awards#site-map | Python Community Awards | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> News & Community >>> Community Awards Python Community Awards Python Software Foundation Community Service Awards are given to members of the community who significantly improve the Foundation's fulfillment of its mission. Python Software Foundation Distinguished Service Awards are given to members of the community whose long-term efforts have significantly influenced and shaped the Python community. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://dev.to/t/linux | Linux - 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 Linux Follow Hide What are clouds made of? Linux servers, mostly. Create Post submission guidelines Articles and discussions should be directly related to Linux operating systems. Questions are encouraged (see the #help tag). Content with the main focus on bash or the Unix shell is permitted, but don't forget to add the #bash or #unix tag as you see it fitting. Articles mainly about WSL should be tagged with #wsl instead of #linux. about #linux Linux is a family of free and open source operating systems built on top of the Linux kernel, first released on 1991 by Linus Torvalds. Older #linux posts 1 2 3 4 5 6 7 8 9 … 75 … 427 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu 🩺 How I Troubleshoot an EC2 Instance in the Real World (Using Instance Diagnostics) Venkata Pavan Vishnu Rachapudi Venkata Pavan Vishnu Rachapudi Venkata Pavan Vishnu Rachapudi Follow for AWS Community Builders Jan 12 🩺 How I Troubleshoot an EC2 Instance in the Real World (Using Instance Diagnostics) # aws # ec2 # linux # cloud 4 reactions Comments Add Comment 5 min read Your "Atomic" Deploys Probably Aren't Atomic mojoatomic mojoatomic mojoatomic Follow Jan 12 Your "Atomic" Deploys Probably Aren't Atomic # devops # deployment # linux # macos Comments Add Comment 3 min read counter Query Filter Query Filter Query Filter Follow Jan 12 counter # automation # bash # database # linux Comments Add Comment 1 min read Bluefin (Atomic) Linux is for Tinkerers Frank Kmiec Frank Kmiec Frank Kmiec Follow Jan 12 Bluefin (Atomic) Linux is for Tinkerers # linux # atomic # bluefin # immutable Comments Add Comment 5 min read The Linux Power User Handbook: From Daily Driver to Productivity Machine MD. HABIBULLAH SHARIF MD. HABIBULLAH SHARIF MD. HABIBULLAH SHARIF Follow Jan 12 The Linux Power User Handbook: From Daily Driver to Productivity Machine # linux # productivity # commandline # bash 1 reaction Comments Add Comment 23 min read Day 1 of Learning Linux & GitHub 🚀 Nishant Nishant Nishant Follow Jan 12 Day 1 of Learning Linux & GitHub 🚀 # linux # mlops # ai # learninginpublic 1 reaction Comments Add Comment 1 min read Getting Started with Ollama for Local LLMs Bernard K Bernard K Bernard K Follow Jan 12 Getting Started with Ollama for Local LLMs # llm # local # linux # mac Comments Add Comment 2 min read Week 4 Firewall Labs: 4 Production-Ready Firewall Scenarios with iptables fosres fosres fosres Follow Jan 12 Week 4 Firewall Labs: 4 Production-Ready Firewall Scenarios with iptables # security # linux # networking # cybersecurity Comments Add Comment 17 min read How to get virtual display outputs on Linux without using a dummy plug Fox Fox Fox Follow Jan 9 How to get virtual display outputs on Linux without using a dummy plug # linux # archlinux Comments Add Comment 4 min read Installing Arch Linux in 2026 (step-by-step) ZionS1_1 ZionS1_1 ZionS1_1 Follow Jan 11 Installing Arch Linux in 2026 (step-by-step) # bash # archlinux # linux # tutorial Comments Add Comment 5 min read Linux Learning Journey – Day 2: Command-Line Practice & System Familiarity 🐧 Avinash wagh Avinash wagh Avinash wagh Follow Jan 12 Linux Learning Journey – Day 2: Command-Line Practice & System Familiarity 🐧 # linux # ubuntu # aws # learning 1 reaction Comments Add Comment 1 min read Setting Up Your Own Linux Server with Hetzner: A Technical Guide ITpraktika.com ITpraktika.com ITpraktika.com Follow Jan 11 Setting Up Your Own Linux Server with Hetzner: A Technical Guide # linux # devops # serverless # tutorial Comments Add Comment 6 min read Understanding Device Tree in Android SBC Development Danie Brooks Danie Brooks Danie Brooks Follow Jan 11 Understanding Device Tree in Android SBC Development # dts # kerne # linux # android Comments Add Comment 5 min read Kubernetes Persistence Series Part 2: The Foundation — From systemd to Control Plane Vincent Du Vincent Du Vincent Du Follow Jan 11 Kubernetes Persistence Series Part 2: The Foundation — From systemd to Control Plane # kubernetes # devops # linux # architecture 8 reactions Comments Add Comment 4 min read Linux File & Directory Operations for DevOps — v1.0 Chetan Tekam Chetan Tekam Chetan Tekam Follow Jan 11 Linux File & Directory Operations for DevOps — v1.0 # beginners # linux # cloud # devops Comments Add Comment 2 min read Linux Monitoring & Alerting: Command-Line Mastery for DevOps Sajja Sudhakararao Sajja Sudhakararao Sajja Sudhakararao Follow Jan 11 Linux Monitoring & Alerting: Command-Line Mastery for DevOps # devops # linux # bash # shell Comments Add Comment 4 min read Claiming WSL Disk Space Paolo Paolo Paolo Follow Jan 12 Claiming WSL Disk Space # linux # microsoft # productivity # tooling Comments Add Comment 2 min read Week 4 Network Packet Tracing Challenge fosres fosres fosres Follow Jan 10 Week 4 Network Packet Tracing Challenge # security # networking # linux # interview Comments Add Comment 8 min read Things I Wish I Knew as a Junior Developer Arauly Technologies Pvt Ltd. Arauly Technologies Pvt Ltd. Arauly Technologies Pvt Ltd. Follow Jan 12 Things I Wish I Knew as a Junior Developer # programming # website # wordpress # linux 2 reactions Comments Add Comment 3 min read VitaGuard: My First Real-Time Linux System Health Monitor in Bash Danielius Navickas Danielius Navickas Danielius Navickas Follow Jan 10 VitaGuard: My First Real-Time Linux System Health Monitor in Bash # linux # ubuntu # tooling # devops Comments Add Comment 2 min read i made this project syswaifu, shows your system stats with random waifu image. Ovi ren Ovi ren Ovi ren Follow Jan 10 i made this project syswaifu, shows your system stats with random waifu image. # showdev # tooling # cli # linux Comments Add Comment 1 min read GRPM v0.5.0: 75% Gentoo Coverage — Rapid Development Complete Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 10 GRPM v0.5.0: 75% Gentoo Coverage — Rapid Development Complete # go # linux # opensource # packagemanager Comments Add Comment 4 min read I'm in 3rd Year - Here's My Complete OS Guide for Campus Placements 📚 Rajat Parihar Rajat Parihar Rajat Parihar Follow Jan 9 I'm in 3rd Year - Here's My Complete OS Guide for Campus Placements 📚 # operatingsystems # placements # computerscience # linux 5 reactions Comments Add Comment 25 min read From Linux Primitives to Docker Swarm: A Deep Dive into Container Networking 🚀 Christian Ameachi Christian Ameachi Christian Ameachi Follow Jan 9 From Linux Primitives to Docker Swarm: A Deep Dive into Container Networking 🚀 # devops # docker # linux # networking 3 reactions Comments Add Comment 2 min read stangri's OpenWrt packages updates Stan Grishin Stan Grishin Stan Grishin Follow Jan 10 stangri's OpenWrt packages updates # linux # networking # opensource # tooling Comments Add Comment 1 min read loading... trending guides/resources Linux Without Fanboyism: An Honest Developer’s Perspective DevOps From Scratch: Entry #01 Advent of Cyber 2025: Day 1 Writeup & SideQuest | TryHackMe Fedora 43 Post-Install Guide: 10 Essential Things to Do After Installing The Weirdest Linux Distros That Shouldn’t Exist (But Absolutely Do) Advent of Cyber 2025: Day 2 Writeup | TryHackMe Navigating the Switch: How to Choose the Right Linux Distro in 2026 Running Local AI on Linux With GPU: Ollama + Open WebUI + Gemma Sync any Linux folder to Google drive using Rclone + systemd. NVIDIA Drops GTX 900/1000 Support in 590 Driver - Getting a Fix on Arch Linux Setting up an encrypted secondary drive on Linux Spotify Connect, Raspberry Pi, AirPlay & HomePod - because simple audio setups are boring Observations from Finetuning Gemma Model on Strix Halo (Fedora 43) Running Firefox in Docker? Yes, with a GUI and noVNC! Fixing WebView2 Issues in Linux Bottles: How I Got It Working How I Turned an Old Phone into a Linux Server My Smooth Journey Setting Up Dual Boot: Windows + Fedora Workstation Linux 🚀🐧 MacOS on debian QEMU KVM Redox OS: Is the Future of Operating Systems Written in Rust? Hyprland 0.52.2+ for Fedora — Clean COPR Build 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://www.python.org/community/awards#content | Python Community Awards | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> News & Community >>> Community Awards Python Community Awards Python Software Foundation Community Service Awards are given to members of the community who significantly improve the Foundation's fulfillment of its mission. Python Software Foundation Distinguished Service Awards are given to members of the community whose long-term efforts have significantly influenced and shaped the Python community. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://www.python.org/download/alternatives#content | Alternative Python implementations | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Alternative Python implementations This site hosts the "traditional" implementation of Python (nicknamed CPython). A number of alternative implementations are available as well, namely PyPy (a fast implementation of Python with a JIT compiler) IronPython (Python running on .NET) MicroPython (Python running on microcontrollers and in the web browser ) Stackless Python (a branch of CPython supporting microthreads) Jython (Python running on the Java Virtual Machine) GraalPy (embeddable Python runtime for Java) Other parties have repackaged CPython. These re-packagings often include more libraries or are specialized for a particular application: Anaconda Python (a full Python distribution for data management, analysis and visualization of large data sets) ActiveState ActivePython (commercial and community versions, including scientific computing modules) Nuitka (a compiler that packages user code with CPython into a static binary for improved performance and IP protection) pyodide (a Python distribution for the browser and Node.js based on WebAssembly) WinPython (a portable scientific Python distribution for Windows) Python(x, y) (Scientific-oriented distribution based on Qt and Spyder) Conceptive Python SDK (targets business, desktop and database applications) PyIMSL Studio (a commercial distribution for numerical analysis – free for non-commercial use) eGenix PyRun (a portable Python runtime, complete with stdlib, frozen into a single 3.5MB - 13MB executable file) If you want to host and run Python in the cloud, these implementations may be right for you: PythonAnywhere (freemium hosted Python installation which lets you run Python in the browser, e.g. for tutorials, showcases) The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://docs.python.org/3/library/ctypes.html#module-ctypes | ctypes — A foreign function library for Python — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents ctypes — A foreign function library for Python ctypes tutorial Loading dynamic link libraries Accessing functions from loaded dlls Calling functions Fundamental data types Calling functions, continued Calling variadic functions Calling functions with your own custom data types Specifying the required argument types (function prototypes) Return types Passing pointers (or: passing parameters by reference) Structures and unions Structure/union layout, alignment and byte order Bit fields in structures and unions Arrays Pointers Thread safety without the GIL Type conversions Incomplete Types Callback functions Accessing values exported from dlls Surprises Variable-sized data types ctypes reference Finding shared libraries Listing loaded shared libraries Loading shared libraries Foreign functions Function prototypes Utility functions Data types Fundamental data types Structured data types Arrays and pointers Exceptions Previous topic errno — Standard errno system symbols Next topic Command-line interface libraries This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Generic Operating System Services » ctypes — A foreign function library for Python | Theme Auto Light Dark | ctypes — A foreign function library for Python ¶ Source code: Lib/ctypes ctypes is a foreign function library for Python. It provides C compatible data types, and allows calling functions in DLLs or shared libraries. It can be used to wrap these libraries in pure Python. This is an optional module . If it is missing from your copy of CPython, look for documentation from your distributor (that is, whoever provided Python to you). If you are the distributor, see Requirements for optional modules . ctypes tutorial ¶ Note: The code samples in this tutorial use doctest to make sure that they actually work. Since some code samples behave differently under Linux, Windows, or macOS, they contain doctest directives in comments. Note: Some code samples reference the ctypes c_int type. On platforms where sizeof(long) == sizeof(int) it is an alias to c_long . So, you should not be confused if c_long is printed if you would expect c_int — they are actually the same type. Loading dynamic link libraries ¶ ctypes exports the cdll , and on Windows windll and oledll objects, for loading dynamic link libraries. You load libraries by accessing them as attributes of these objects. cdll loads libraries which export functions using the standard cdecl calling convention, while windll libraries call functions using the stdcall calling convention. oledll also uses the stdcall calling convention, and assumes the functions return a Windows HRESULT error code. The error code is used to automatically raise an OSError exception when the function call fails. Changed in version 3.3: Windows errors used to raise WindowsError , which is now an alias of OSError . Here are some examples for Windows. Note that msvcrt is the MS standard C library containing most standard C functions, and uses the cdecl calling convention: >>> from ctypes import * >>> print ( windll . kernel32 ) <WinDLL 'kernel32', handle ... at ...> >>> print ( cdll . msvcrt ) <CDLL 'msvcrt', handle ... at ...> >>> libc = cdll . msvcrt >>> Windows appends the usual .dll file suffix automatically. Note Accessing the standard C library through cdll.msvcrt will use an outdated version of the library that may be incompatible with the one being used by Python. Where possible, use native Python functionality, or else import and use the msvcrt module. On Linux, it is required to specify the filename including the extension to load a library, so attribute access can not be used to load libraries. Either the LoadLibrary() method of the dll loaders should be used, or you should load the library by creating an instance of CDLL by calling the constructor: >>> cdll . LoadLibrary ( "libc.so.6" ) <CDLL 'libc.so.6', handle ... at ...> >>> libc = CDLL ( "libc.so.6" ) >>> libc <CDLL 'libc.so.6', handle ... at ...> >>> Accessing functions from loaded dlls ¶ Functions are accessed as attributes of dll objects: >>> libc . printf <_FuncPtr object at 0x...> >>> print ( windll . kernel32 . GetModuleHandleA ) <_FuncPtr object at 0x...> >>> print ( windll . kernel32 . MyOwnFunction ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> File "ctypes.py" , line 239 , in __getattr__ func = _StdcallFuncPtr ( name , self ) AttributeError : function 'MyOwnFunction' not found >>> Note that win32 system dlls like kernel32 and user32 often export ANSI as well as UNICODE versions of a function. The UNICODE version is exported with a W appended to the name, while the ANSI version is exported with an A appended to the name. The win32 GetModuleHandle function, which returns a module handle for a given module name, has the following C prototype, and a macro is used to expose one of them as GetModuleHandle depending on whether UNICODE is defined or not: /* ANSI version */ HMODULE GetModuleHandleA ( LPCSTR lpModuleName ); /* UNICODE version */ HMODULE GetModuleHandleW ( LPCWSTR lpModuleName ); windll does not try to select one of them by magic, you must access the version you need by specifying GetModuleHandleA or GetModuleHandleW explicitly, and then call it with bytes or string objects respectively. Sometimes, dlls export functions with names which aren’t valid Python identifiers, like "??2@YAPAXI@Z" . In this case you have to use getattr() to retrieve the function: >>> getattr ( cdll . msvcrt , "??2@YAPAXI@Z" ) <_FuncPtr object at 0x...> >>> On Windows, some dlls export functions not by name but by ordinal. These functions can be accessed by indexing the dll object with the ordinal number: >>> cdll . kernel32 [ 1 ] <_FuncPtr object at 0x...> >>> cdll . kernel32 [ 0 ] Traceback (most recent call last): File "<stdin>" , line 1 , in <module> File "ctypes.py" , line 310 , in __getitem__ func = _StdcallFuncPtr ( name , self ) AttributeError : function ordinal 0 not found >>> Calling functions ¶ You can call these functions like any other Python callable. This example uses the rand() function, which takes no arguments and returns a pseudo-random integer: >>> print ( libc . rand ()) 1804289383 On Windows, you can call the GetModuleHandleA() function, which returns a win32 module handle (passing None as single argument to call it with a NULL pointer): >>> print ( hex ( windll . kernel32 . GetModuleHandleA ( None ))) 0x1d000000 >>> ValueError is raised when you call an stdcall function with the cdecl calling convention, or vice versa: >>> cdll . kernel32 . GetModuleHandleA ( None ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> ValueError : Procedure probably called with not enough arguments (4 bytes missing) >>> >>> windll . msvcrt . printf ( b "spam" ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> ValueError : Procedure probably called with too many arguments (4 bytes in excess) >>> To find out the correct calling convention you have to look into the C header file or the documentation for the function you want to call. On Windows, ctypes uses win32 structured exception handling to prevent crashes from general protection faults when functions are called with invalid argument values: >>> windll . kernel32 . GetModuleHandleA ( 32 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> OSError : exception: access violation reading 0x00000020 >>> There are, however, enough ways to crash Python with ctypes , so you should be careful anyway. The faulthandler module can be helpful in debugging crashes (e.g. from segmentation faults produced by erroneous C library calls). None , integers, bytes objects and (unicode) strings are the only native Python objects that can directly be used as parameters in these function calls. None is passed as a C NULL pointer, bytes objects and strings are passed as pointer to the memory block that contains their data ( char * or wchar_t * ). Python integers are passed as the platform’s default C int type, their value is masked to fit into the C type. Before we move on calling functions with other parameter types, we have to learn more about ctypes data types. Fundamental data types ¶ ctypes defines a number of primitive C compatible data types: ctypes type C type Python type c_bool _Bool bool (1) c_char char 1-character bytes object c_wchar wchar_t 1-character string c_byte char int c_ubyte unsigned char int c_short short int c_ushort unsigned short int c_int int int c_int8 int8_t int c_int16 int16_t int c_int32 int32_t int c_int64 int64_t int c_uint unsigned int int c_uint8 uint8_t int c_uint16 uint16_t int c_uint32 uint32_t int c_uint64 uint64_t int c_long long int c_ulong unsigned long int c_longlong __int64 or long long int c_ulonglong unsigned __int64 or unsigned long long int c_size_t size_t int c_ssize_t ssize_t or Py_ssize_t int c_time_t time_t int c_float float float c_double double float c_longdouble long double float c_char_p char * (NUL terminated) bytes object or None c_wchar_p wchar_t * (NUL terminated) string or None c_void_p void * int or None The constructor accepts any object with a truth value. Additionally, if IEC 60559 compatible complex arithmetic (Annex G) is supported in both C and libffi , the following complex types are available: ctypes type C type Python type c_float_complex float complex complex c_double_complex double complex complex c_longdouble_complex long double complex complex All these types can be created by calling them with an optional initializer of the correct type and value: >>> c_int () c_long(0) >>> c_wchar_p ( "Hello, World" ) c_wchar_p(140018365411392) >>> c_ushort ( - 3 ) c_ushort(65533) >>> Since these types are mutable, their value can also be changed afterwards: >>> i = c_int ( 42 ) >>> print ( i ) c_long(42) >>> print ( i . value ) 42 >>> i . value = - 99 >>> print ( i . value ) -99 >>> Assigning a new value to instances of the pointer types c_char_p , c_wchar_p , and c_void_p changes the memory location they point to, not the contents of the memory block (of course not, because Python string objects are immutable): >>> s = "Hello, World" >>> c_s = c_wchar_p ( s ) >>> print ( c_s ) c_wchar_p(139966785747344) >>> print ( c_s . value ) Hello World >>> c_s . value = "Hi, there" >>> print ( c_s ) # the memory location has changed c_wchar_p(139966783348904) >>> print ( c_s . value ) Hi, there >>> print ( s ) # first object is unchanged Hello, World >>> You should be careful, however, not to pass them to functions expecting pointers to mutable memory. If you need mutable memory blocks, ctypes has a create_string_buffer() function which creates these in various ways. The current memory block contents can be accessed (or changed) with the raw property; if you want to access it as NUL terminated string, use the value property: >>> from ctypes import * >>> p = create_string_buffer ( 3 ) # create a 3 byte buffer, initialized to NUL bytes >>> print ( sizeof ( p ), repr ( p . raw )) 3 b'\x00\x00\x00' >>> p = create_string_buffer ( b "Hello" ) # create a buffer containing a NUL terminated string >>> print ( sizeof ( p ), repr ( p . raw )) 6 b'Hello\x00' >>> print ( repr ( p . value )) b'Hello' >>> p = create_string_buffer ( b "Hello" , 10 ) # create a 10 byte buffer >>> print ( sizeof ( p ), repr ( p . raw )) 10 b'Hello\x00\x00\x00\x00\x00' >>> p . value = b "Hi" >>> print ( sizeof ( p ), repr ( p . raw )) 10 b'Hi\x00lo\x00\x00\x00\x00\x00' >>> The create_string_buffer() function replaces the old c_buffer() function (which is still available as an alias). To create a mutable memory block containing unicode characters of the C type wchar_t , use the create_unicode_buffer() function. Calling functions, continued ¶ Note that printf prints to the real standard output channel, not to sys.stdout , so these examples will only work at the console prompt, not from within IDLE or PythonWin : >>> printf = libc . printf >>> printf ( b "Hello, %s \n " , b "World!" ) Hello, World! 14 >>> printf ( b "Hello, %S \n " , "World!" ) Hello, World! 14 >>> printf ( b " %d bottles of beer \n " , 42 ) 42 bottles of beer 19 >>> printf ( b " %f bottles of beer \n " , 42.5 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> ctypes.ArgumentError : argument 2: TypeError: Don't know how to convert parameter 2 >>> As has been mentioned before, all Python types except integers, strings, and bytes objects have to be wrapped in their corresponding ctypes type, so that they can be converted to the required C data type: >>> printf ( b "An int %d , a double %f \n " , 1234 , c_double ( 3.14 )) An int 1234, a double 3.140000 31 >>> Calling variadic functions ¶ On a lot of platforms calling variadic functions through ctypes is exactly the same as calling functions with a fixed number of parameters. On some platforms, and in particular ARM64 for Apple Platforms, the calling convention for variadic functions is different than that for regular functions. On those platforms it is required to specify the argtypes attribute for the regular, non-variadic, function arguments: libc . printf . argtypes = [ ctypes . c_char_p ] Because specifying the attribute does not inhibit portability it is advised to always specify argtypes for all variadic functions. Calling functions with your own custom data types ¶ You can also customize ctypes argument conversion to allow instances of your own classes be used as function arguments. ctypes looks for an _as_parameter_ attribute and uses this as the function argument. The attribute must be an integer, string, bytes, a ctypes instance, or an object with an _as_parameter_ attribute: >>> class Bottles : ... def __init__ ( self , number ): ... self . _as_parameter_ = number ... >>> bottles = Bottles ( 42 ) >>> printf ( b " %d bottles of beer \n " , bottles ) 42 bottles of beer 19 >>> If you don’t want to store the instance’s data in the _as_parameter_ instance variable, you could define a property which makes the attribute available on request. Specifying the required argument types (function prototypes) ¶ It is possible to specify the required argument types of functions exported from DLLs by setting the argtypes attribute. argtypes must be a sequence of C data types (the printf() function is probably not a good example here, because it takes a variable number and different types of parameters depending on the format string, on the other hand this is quite handy to experiment with this feature): >>> printf . argtypes = [ c_char_p , c_char_p , c_int , c_double ] >>> printf ( b "String ' %s ', Int %d , Double %f \n " , b "Hi" , 10 , 2.2 ) String 'Hi', Int 10, Double 2.200000 37 >>> Specifying a format protects against incompatible argument types (just as a prototype for a C function), and tries to convert the arguments to valid types: >>> printf ( b " %d %d %d " , 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> ctypes.ArgumentError : argument 2: TypeError: 'int' object cannot be interpreted as ctypes.c_char_p >>> printf ( b " %s %d %f \n " , b "X" , 2 , 3 ) X 2 3.000000 13 >>> If you have defined your own classes which you pass to function calls, you have to implement a from_param() class method for them to be able to use them in the argtypes sequence. The from_param() class method receives the Python object passed to the function call, it should do a typecheck or whatever is needed to make sure this object is acceptable, and then return the object itself, its _as_parameter_ attribute, or whatever you want to pass as the C function argument in this case. Again, the result should be an integer, string, bytes, a ctypes instance, or an object with an _as_parameter_ attribute. Return types ¶ By default functions are assumed to return the C int type. Other return types can be specified by setting the restype attribute of the function object. The C prototype of time() is time_t time(time_t *) . Because time_t might be of a different type than the default return type int , you should specify the restype attribute: >>> libc . time . restype = c_time_t The argument types can be specified using argtypes : >>> libc . time . argtypes = ( POINTER ( c_time_t ),) To call the function with a NULL pointer as first argument, use None : >>> print ( libc . time ( None )) 1150640792 Here is a more advanced example, it uses the strchr() function, which expects a string pointer and a char, and returns a pointer to a string: >>> strchr = libc . strchr >>> strchr ( b "abcdef" , ord ( "d" )) 8059983 >>> strchr . restype = c_char_p # c_char_p is a pointer to a string >>> strchr ( b "abcdef" , ord ( "d" )) b'def' >>> print ( strchr ( b "abcdef" , ord ( "x" ))) None >>> If you want to avoid the ord("x") calls above, you can set the argtypes attribute, and the second argument will be converted from a single character Python bytes object into a C char: >>> strchr . restype = c_char_p >>> strchr . argtypes = [ c_char_p , c_char ] >>> strchr ( b "abcdef" , b "d" ) b'def' >>> strchr ( b "abcdef" , b "def" ) Traceback (most recent call last): ctypes.ArgumentError : argument 2: TypeError: one character bytes, bytearray or integer expected >>> print ( strchr ( b "abcdef" , b "x" )) None >>> strchr ( b "abcdef" , b "d" ) b'def' >>> You can also use a callable Python object (a function or a class for example) as the restype attribute, if the foreign function returns an integer. The callable will be called with the integer the C function returns, and the result of this call will be used as the result of your function call. This is useful to check for error return values and automatically raise an exception: >>> GetModuleHandle = windll . kernel32 . GetModuleHandleA >>> def ValidHandle ( value ): ... if value == 0 : ... raise WinError () ... return value ... >>> >>> GetModuleHandle . restype = ValidHandle >>> GetModuleHandle ( None ) 486539264 >>> GetModuleHandle ( "something silly" ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> File "<stdin>" , line 3 , in ValidHandle OSError : [Errno 126] The specified module could not be found. >>> WinError is a function which will call Windows FormatMessage() api to get the string representation of an error code, and returns an exception. WinError takes an optional error code parameter, if no one is used, it calls GetLastError() to retrieve it. Please note that a much more powerful error checking mechanism is available through the errcheck attribute; see the reference manual for details. Passing pointers (or: passing parameters by reference) ¶ Sometimes a C api function expects a pointer to a data type as parameter, probably to write into the corresponding location, or if the data is too large to be passed by value. This is also known as passing parameters by reference . ctypes exports the byref() function which is used to pass parameters by reference. The same effect can be achieved with the pointer() function, although pointer() does a lot more work since it constructs a real pointer object, so it is faster to use byref() if you don’t need the pointer object in Python itself: >>> i = c_int () >>> f = c_float () >>> s = create_string_buffer ( b ' \000 ' * 32 ) >>> print ( i . value , f . value , repr ( s . value )) 0 0.0 b'' >>> libc . sscanf ( b "1 3.14 Hello" , b " %d %f %s " , ... byref ( i ), byref ( f ), s ) 3 >>> print ( i . value , f . value , repr ( s . value )) 1 3.1400001049 b'Hello' >>> Structures and unions ¶ Structures and unions must derive from the Structure and Union base classes which are defined in the ctypes module. Each subclass must define a _fields_ attribute. _fields_ must be a list of 2-tuples , containing a field name and a field type . The field type must be a ctypes type like c_int , or any other derived ctypes type: structure, union, array, pointer. Here is a simple example of a POINT structure, which contains two integers named x and y , and also shows how to initialize a structure in the constructor: >>> from ctypes import * >>> class POINT ( Structure ): ... _fields_ = [( "x" , c_int ), ... ( "y" , c_int )] ... >>> point = POINT ( 10 , 20 ) >>> print ( point . x , point . y ) 10 20 >>> point = POINT ( y = 5 ) >>> print ( point . x , point . y ) 0 5 >>> POINT ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : too many initializers >>> You can, however, build much more complicated structures. A structure can itself contain other structures by using a structure as a field type. Here is a RECT structure which contains two POINTs named upperleft and lowerright : >>> class RECT ( Structure ): ... _fields_ = [( "upperleft" , POINT ), ... ( "lowerright" , POINT )] ... >>> rc = RECT ( point ) >>> print ( rc . upperleft . x , rc . upperleft . y ) 0 5 >>> print ( rc . lowerright . x , rc . lowerright . y ) 0 0 >>> Nested structures can also be initialized in the constructor in several ways: >>> r = RECT ( POINT ( 1 , 2 ), POINT ( 3 , 4 )) >>> r = RECT (( 1 , 2 ), ( 3 , 4 )) Field descriptor s can be retrieved from the class , they are useful for debugging because they can provide useful information. See CField : >>> POINT . x <ctypes.CField 'x' type=c_int, ofs=0, size=4> >>> POINT . y <ctypes.CField 'y' type=c_int, ofs=4, size=4> >>> Warning ctypes does not support passing unions or structures with bit-fields to functions by value. While this may work on 32-bit x86, it’s not guaranteed by the library to work in the general case. Unions and structures with bit-fields should always be passed to functions by pointer. Structure/union layout, alignment and byte order ¶ By default, Structure and Union fields are laid out in the same way the C compiler does it. It is possible to override this behavior entirely by specifying a _layout_ class attribute in the subclass definition; see the attribute documentation for details. It is possible to specify the maximum alignment for the fields and/or for the structure itself by setting the class attributes _pack_ and/or _align_ , respectively. See the attribute documentation for details. ctypes uses the native byte order for Structures and Unions. To build structures with non-native byte order, you can use one of the BigEndianStructure , LittleEndianStructure , BigEndianUnion , and LittleEndianUnion base classes. These classes cannot contain pointer fields. Bit fields in structures and unions ¶ It is possible to create structures and unions containing bit fields. Bit fields are only possible for integer fields, the bit width is specified as the third item in the _fields_ tuples: >>> class Int ( Structure ): ... _fields_ = [( "first_16" , c_int , 16 ), ... ( "second_16" , c_int , 16 )] ... >>> print ( Int . first_16 ) <ctypes.CField 'first_16' type=c_int, ofs=0, bit_size=16, bit_offset=0> >>> print ( Int . second_16 ) <ctypes.CField 'second_16' type=c_int, ofs=0, bit_size=16, bit_offset=16> It is important to note that bit field allocation and layout in memory are not defined as a C standard; their implementation is compiler-specific. By default, Python will attempt to match the behavior of a “native” compiler for the current platform. See the _layout_ attribute for details on the default behavior and how to change it. Arrays ¶ Arrays are sequences, containing a fixed number of instances of the same type. The recommended way to create array types is by multiplying a data type with a positive integer: TenPointsArrayType = POINT * 10 Here is an example of a somewhat artificial data type, a structure containing 4 POINTs among other stuff: >>> from ctypes import * >>> class POINT ( Structure ): ... _fields_ = ( "x" , c_int ), ( "y" , c_int ) ... >>> class MyStruct ( Structure ): ... _fields_ = [( "a" , c_int ), ... ( "b" , c_float ), ... ( "point_array" , POINT * 4 )] >>> >>> print ( len ( MyStruct () . point_array )) 4 >>> Instances are created in the usual way, by calling the class: arr = TenPointsArrayType () for pt in arr : print ( pt . x , pt . y ) The above code print a series of 0 0 lines, because the array contents is initialized to zeros. Initializers of the correct type can also be specified: >>> from ctypes import * >>> TenIntegers = c_int * 10 >>> ii = TenIntegers ( 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 ) >>> print ( ii ) <c_long_Array_10 object at 0x...> >>> for i in ii : print ( i , end = " " ) ... 1 2 3 4 5 6 7 8 9 10 >>> Pointers ¶ Pointer instances are created by calling the pointer() function on a ctypes type: >>> from ctypes import * >>> i = c_int ( 42 ) >>> pi = pointer ( i ) >>> Pointer instances have a contents attribute which returns the object to which the pointer points, the i object above: >>> pi . contents c_long(42) >>> Note that ctypes does not have OOR (original object return), it constructs a new, equivalent object each time you retrieve an attribute: >>> pi . contents is i False >>> pi . contents is pi . contents False >>> Assigning another c_int instance to the pointer’s contents attribute would cause the pointer to point to the memory location where this is stored: >>> i = c_int ( 99 ) >>> pi . contents = i >>> pi . contents c_long(99) >>> Pointer instances can also be indexed with integers: >>> pi [ 0 ] 99 >>> Assigning to an integer index changes the pointed to value: >>> print ( i ) c_long(99) >>> pi [ 0 ] = 22 >>> print ( i ) c_long(22) >>> It is also possible to use indexes different from 0, but you must know what you’re doing, just as in C: You can access or change arbitrary memory locations. Generally you only use this feature if you receive a pointer from a C function, and you know that the pointer actually points to an array instead of a single item. Behind the scenes, the pointer() function does more than simply create pointer instances, it has to create pointer types first. This is done with the POINTER() function, which accepts any ctypes type, and returns a new type: >>> PI = POINTER ( c_int ) >>> PI <class 'ctypes.LP_c_long'> >>> PI ( 42 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : expected c_long instead of int >>> PI ( c_int ( 42 )) <ctypes.LP_c_long object at 0x...> >>> Calling the pointer type without an argument creates a NULL pointer. NULL pointers have a False boolean value: >>> null_ptr = POINTER ( c_int )() >>> print ( bool ( null_ptr )) False >>> ctypes checks for NULL when dereferencing pointers (but dereferencing invalid non- NULL pointers would crash Python): >>> null_ptr [ 0 ] Traceback (most recent call last): .... ValueError : NULL pointer access >>> >>> null_ptr [ 0 ] = 1234 Traceback (most recent call last): .... ValueError : NULL pointer access >>> Thread safety without the GIL ¶ From Python 3.13 onward, the GIL can be disabled on free threaded builds. In ctypes, reads and writes to a single object concurrently is safe, but not across multiple objects: >>> number = c_int ( 42 ) >>> pointer_a = pointer ( number ) >>> pointer_b = pointer ( number ) In the above, it’s only safe for one object to read and write to the address at once if the GIL is disabled. So, pointer_a can be shared and written to across multiple threads, but only if pointer_b is not also attempting to do the same. If this is an issue, consider using a threading.Lock to synchronize access to memory: >>> import threading >>> lock = threading . Lock () >>> # Thread 1 >>> with lock : ... pointer_a . contents = 24 >>> # Thread 2 >>> with lock : ... pointer_b . contents = 42 Type conversions ¶ Usually, ctypes does strict type checking. This means, if you have POINTER(c_int) in the argtypes list of a function or as the type of a member field in a structure definition, only instances of exactly the same type are accepted. There are some exceptions to this rule, where ctypes accepts other objects. For example, you can pass compatible array instances instead of pointer types. So, for POINTER(c_int) , ctypes accepts an array of c_int: >>> class Bar ( Structure ): ... _fields_ = [( "count" , c_int ), ( "values" , POINTER ( c_int ))] ... >>> bar = Bar () >>> bar . values = ( c_int * 3 )( 1 , 2 , 3 ) >>> bar . count = 3 >>> for i in range ( bar . count ): ... print ( bar . values [ i ]) ... 1 2 3 >>> In addition, if a function argument is explicitly declared to be a pointer type (such as POINTER(c_int) ) in argtypes , an object of the pointed type ( c_int in this case) can be passed to the function. ctypes will apply the required byref() conversion in this case automatically. To set a POINTER type field to NULL , you can assign None : >>> bar . values = None >>> Sometimes you have instances of incompatible types. In C, you can cast one type into another type. ctypes provides a cast() function which can be used in the same way. The Bar structure defined above accepts POINTER(c_int) pointers or c_int arrays for its values field, but not instances of other types: >>> bar . values = ( c_byte * 4 )() Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : incompatible types, c_byte_Array_4 instance instead of LP_c_long instance >>> For these cases, the cast() function is handy. The cast() function can be used to cast a ctypes instance into a pointer to a different ctypes data type. cast() takes two parameters, a ctypes object that is or can be converted to a pointer of some kind, and a ctypes pointer type. It returns an instance of the second argument, which references the same memory block as the first argument: >>> a = ( c_byte * 4 )() >>> cast ( a , POINTER ( c_int )) <ctypes.LP_c_long object at ...> >>> So, cast() can be used to assign to the values field of Bar the structure: >>> bar = Bar () >>> bar . values = cast (( c_byte * 4 )(), POINTER ( c_int )) >>> print ( bar . values [ 0 ]) 0 >>> Incomplete Types ¶ Incomplete Types are structures, unions or arrays whose members are not yet specified. In C, they are specified by forward declarations, which are defined later: struct cell ; /* forward declaration */ struct cell { char * name ; struct cell * next ; }; The straightforward translation into ctypes code would be this, but it does not work: >>> class cell ( Structure ): ... _fields_ = [( "name" , c_char_p ), ... ( "next" , POINTER ( cell ))] ... Traceback (most recent call last): File "<stdin>" , line 1 , in <module> File "<stdin>" , line 2 , in cell NameError : name 'cell' is not defined >>> because the new class cell is not available in the class statement itself. In ctypes , we can define the cell class and set the _fields_ attribute later, after the class statement: >>> from ctypes import * >>> class cell ( Structure ): ... pass ... >>> cell . _fields_ = [( "name" , c_char_p ), ... ( "next" , POINTER ( cell ))] >>> Let’s try it. We create two instances of cell , and let them point to each other, and finally follow the pointer chain a few times: >>> c1 = cell () >>> c1 . name = b "foo" >>> c2 = cell () >>> c2 . name = b "bar" >>> c1 . next = pointer ( c2 ) >>> c2 . next = pointer ( c1 ) >>> p = c1 >>> for i in range ( 8 ): ... print ( p . name , end = " " ) ... p = p . next [ 0 ] ... foo bar foo bar foo bar foo bar >>> Callback functions ¶ ctypes allows creating C callable function pointers from Python callables. These are sometimes called callback functions . First, you must create a class for the callback function. The class knows the calling convention, the return type, and the number and types of arguments this function will receive. The CFUNCTYPE() factory function creates types for callback functions using the cdecl calling convention. On Windows, the WINFUNCTYPE() factory function creates types for callback functions using the stdcall calling convention. Both of these factory functions are called with the result type as first argument, and the callback functions expected argument types as the remaining arguments. I will present an example here which uses the standard C library’s qsort() function, that is used to sort items with the help of a callback function. qsort() will be used to sort an array of integers: >>> IntArray5 = c_int * 5 >>> ia = IntArray5 ( 5 , 1 , 7 , 33 , 99 ) >>> qsort = libc . qsort >>> qsort . restype = None >>> qsort() must be called with a pointer to the data to sort, the number of items in the data array, the size of one item, and a pointer to the comparison function, the callback. The callback will then be called with two pointers to items, and it must return a negative integer if the first item is smaller than the second, a zero if they are equal, and a positive integer otherwise. So our callback function receives pointers to integers, and must return an integer. First we create the type for the callback function: >>> CMPFUNC = CFUNCTYPE ( c_int , POINTER ( c_int ), POINTER ( c_int )) >>> To get started, here is a simple callback that shows the values it gets passed: >>> def py_cmp_func ( a , b ): ... print ( "py_cmp_func" , a [ 0 ], b [ 0 ]) ... return 0 ... >>> cmp_func = CMPFUNC ( py_cmp_func ) >>> The result: >>> qsort ( ia , len ( ia ), sizeof ( c_int ), cmp_func ) py_cmp_func 5 1 py_cmp_func 33 99 py_cmp_func 7 33 py_cmp_func 5 7 py_cmp_func 1 7 >>> Now we can actually compare the two items and return a useful result: >>> def py_cmp_func ( a , b ): ... print ( "py_cmp_func" , a [ 0 ], b [ 0 ]) ... return a [ 0 ] - b [ 0 ] ... >>> >>> qsort ( ia , len ( ia ), sizeof ( c_int ), CMPFUNC ( py_cmp_func )) py_cmp_func 5 1 py_cmp_func 33 99 py_cmp_func 7 33 py_cmp_func 1 7 py_cmp_func 5 7 >>> As we can easily check, our array is sorted now: >>> for i in ia : print ( i , end = " " ) ... 1 5 7 33 99 >>> The function factories can be used as decorator factories, so we may as well write: >>> @CFUNCTYPE ( c_int , POINTER ( c_int ), POINTER ( c_int )) ... def py_cmp_func ( a , b ): ... print ( "py_cmp_func" , a [ 0 ], b [ 0 ]) ... return a [ 0 ] - b [ 0 ] ... >>> qsort ( ia , len ( ia ), sizeof ( c_int ), py_cmp_func ) py_cmp_func 5 1 py_cmp_func 33 99 py_cmp_func 7 33 py_cmp_func 1 7 py_cmp_func 5 7 >>> Note Make sure you keep references to CFUNCTYPE() objects as long as they are used from C code. ctypes doesn’t, and if you don’t, they may be garbage collected, crashing your program when a callback is made. Also, note that if the callback function is called in a thread created outside of Python’s control (e.g. by the foreign code that calls the callback), ctypes creates a new dummy Python thread on every invocation. This behavior is correct for most purposes, but it means that values stored with threading.local will not survive across different callbacks, even when those calls are made from the same C thread. Accessing values exported from dlls ¶ Some shared libraries not only export functions, they also export variables. An example in the Python library itself is the Py_Version , Python runtime version number encoded in a single constant integer. ctypes can access values like this with the in_dll() class methods of the type. pythonapi is a predefined symbol giving access to the Python C api: >>> version = ctypes . c_int . in_dll ( ctypes . pythonapi , "Py_Version" ) >>> print ( hex ( version . value )) 0x30c00a0 An extended example which also demonstrates the use of pointers accesses the PyImport_FrozenModules pointer exported by Python. Quoting the docs for that value: This pointer is initialized to point to an array of _frozen records, terminated by one whose members are all NULL or zero. When a frozen module is imported, it is searched in this table. Third-party code could play tricks with this to provide a dynamically created collection of frozen modules. So manipulating this pointer could even prove useful. To restrict the example size, we show only how this table can be read with ctypes : >>> from ctypes import * >>> >>> class struct_frozen ( Structure ): ... _fields_ = [( "name" , c_char_p ), ... ( "code" , POINTER ( c_ubyte )), ... ( "size" , c_int ), ... ( "get_code" , POINTER ( c_ubyte )), # Function pointer ... ] ... >>> We have defined the _frozen data type, so we can get the pointer to the table: >>> FrozenTable = POINTER ( struct_frozen ) >>> table = FrozenTable . in_dll ( pythonapi , "_PyImport_FrozenBootstrap" ) >>> Since table is a pointer to the array of struct_frozen records, we can iterate over it, but we just have to make sure that our loop terminates, because pointers have no size. Sooner or later it would probably crash with an access violation or whatever, so it’s better to break out of the loop when we hit the NULL entry: >>> for item in table : ... if item . name is None : ... break ... print ( item . name . decode ( "ascii" ), item . size ) ... _frozen_importlib 31764 _frozen_importlib_external 41499 zipimport 12345 >>> The fact that standard Python has a frozen module and a frozen package (indicated by the negative size member) is not well known, it is only used for testing. Try it out with import __hello__ for example. Surprises ¶ There are some edges in ctypes where you might expect something other than what actually happens. Consider the following example: >>> from ctypes import * >>> class POINT ( Structure ): ... _fields_ = ( "x" , c_int ), ( "y" , c_int ) ... >>> class RECT ( Structure ): ... _fields_ = ( "a" , POINT ), ( "b" , POINT ) ... >>> p1 = POINT ( 1 , 2 ) >>> p2 = POINT ( 3 , 4 ) >>> rc = RECT ( p1 , p2 ) >>> print ( rc . a . x , rc . a . y , rc . b . x , rc . b . y ) 1 2 3 4 >>> # now swap the two points >>> rc . a , rc . b = rc . b , rc . a >>> print ( rc . a . x , rc . a . y , rc . b . x , rc . b . y ) 3 4 3 4 >>> Hm. We certainly expected the last statement to print 3 4 1 2 . What happened? Here are the steps of the rc.a, rc.b = rc.b, rc.a line above: >>> temp0 , temp1 = rc . b , rc . a >>> rc . a = temp0 >>> rc . b = temp1 >>> Note that temp0 and temp1 are objects still using the internal buffer of the rc object above. So executing rc.a = temp0 copies the buffer contents of temp0 into rc ‘s buffer. This, in turn, changes the contents of temp1 . So, the last assignment rc.b = temp1 , doesn’t have the expected effect. Keep in mind that retrieving sub-objects from Structure, Unions, and Arrays doesn’t copy the sub-object, instead it retrieves a wrapper object accessing the root-object’s underlying buffer. Another example that may behave differently from what one would expect is this: >>> s = c_char_p () >>> s . value = b "abc def ghi" >>> s . value b'abc def ghi' >>> s . value is s . value False >>> Note Objects instantiated from c_char_p can only have their value set to bytes or integers. Why is it printing False ? ctypes instances are objects containing a memory block plus some descriptor s accessing the contents of the memory. Storing a Python object in the memory block does not store the object itself, instead the contents of the object is stored. Accessing the contents again constructs a new Python object each time! Variable-sized data types ¶ ctypes provides some support for variable-sized arrays and structures. The resize() function can be used to resize the memory buffer of an existing ctypes object. The function takes the object as first argument, and the requested size in bytes as the second argument. The memory block cannot be made smaller than the natural memory block specified by the objects type, a ValueError is raised if this is tried: >>> short_array = ( c_short * 4 )() >>> print ( sizeof ( short_array )) 8 >>> resize ( short_array , 4 ) Traceback (most recent call last): ... ValueError : minimum size is 8 >>> resize ( short_array , 32 ) >>> sizeof ( short_array ) 32 >>> sizeof ( type ( short_array )) 8 >>> This is nice and fine, but how would one access the additional elements contained in this array? Since the type still only knows about 4 elements, we get errors accessing other elements: >>> short_array [:] [0, 0, 0, 0] >>> short_array [ 7 ] Traceback (most recent call last): ... IndexError : invalid index >>> Another way to use variable-sized data types with ctypes is to use the dynamic nature of Python, and (re-)define the data type after the required size is already known, on a case by case basis. ctypes reference ¶ Finding shared libraries ¶ When programming in a compiled language, shared libraries are accessed when compiling/linking a program, and when the program is run. The purpose of the find_library() function is to locate a library in a way similar to what the compiler or runtime loader does (on platforms with several versions of a shared library the most recent should be loaded), while the ctypes library loaders act like when a program is run, and call the runtime loader directly. The ctypes.util module provides a function which can help to determine the library to load. ctypes.util. find_library ( name ) Try to find a library and return a pathname. name is the library name without any prefix like lib , suffix like .so , .dylib or version number (this is the form used for the posix linker option -l ). If no library can be found, returns None . The exact functionality is system dependent. On Linux, find_library() tries to run external programs ( /sbin/ldconfig , gcc , objdump and ld ) to find the library file. It returns the filename of the library file. Note that if the output of these programs does not correspond to the dynamic linker used by Python, the result of this function may be misleading. Changed in version 3.6: On Linux, the value of the environment variable LD_LIBRARY_PATH is used when searching for libraries, if a library cannot be found by any other means. Here are some examples: >>> from ctypes.util import find_library >>> find_library ( "m" ) 'libm.so.6' >>> find_library ( "c" ) 'libc.so.6' >>> find_library ( "bz2" ) 'libbz2.so.1.0' >>> On macOS and Android, find_library() uses the system’s standard naming schemes and paths to locate the library, and returns a full pathname if successful: >>> from ctypes.util import find_library >>> find_library ( "c" ) '/usr/lib/libc.dylib' >>> find_library ( "m" ) '/usr/lib/libm.dylib' >>> find_library ( "bz2" ) '/usr/lib/libbz2.dylib' >>> find_library ( "AGL" ) '/System/Library/Frameworks/AGL.framework/AGL' >>> On Windows, find_library() searches along the system search path, and returns the full pathname, but since there is no predefined naming scheme a call like find_library("c") will fail and return None . If wrapping a shared library with ctypes , it may be better to determine the shared library name at development time, and hardcode that into the wrapper module instead of using find_library() to locate the library at runtime. Listing loaded shared libraries ¶ When writing code that relies on code loaded from shared libraries, it can be useful to know which shared libraries have already been loaded into the current process. The ctypes.util module provides the dllist() function, which calls the different APIs provided by the various platforms to help determine which shared libraries have already been loaded into the current process. The exact output of this function will be system dependent. On most platforms, the first entry of this list represents the current process itself, which may be an empty string. For example, on glibc-based Linux, the return may look like: >>> from ctypes.util import dllist >>> dllist () ['', 'linux-vdso.so.1', '/lib/x86_64-linux-gnu/libm.so.6', '/lib/x86_64-linux-gnu/libc.so.6', ... ] Loading shared libraries ¶ There are several ways to load shared libraries into the Python process. One way is to instantiate one of the following classes: class ctypes. CDLL ( name , mode = DEFAULT_MODE , handle = None , use_errno = False , use_last_error = False , winmode = None ) ¶ Instances of this class represent loaded shared libraries. Functions in these libraries use the standard C calling convention, and are assumed to return int . On Windows creating a CDLL instance may fail even if the DLL name exists. When a dependent DLL of the loaded DLL is not found, a OSError error is raised with the message “[WinError 126] The specified module could not be found”. This error message does not contain the name of the missing DLL because the Windows API does not return this information making this error hard to diagnose. To resolve this error and determine which DLL is not found, you need to find the list of dependent DLLs and determine which one is not found using Windows debugging and tracing tools. Changed in version 3.12: The name parameter can now be a path-like object . See also Microsoft DUMPBIN tool – A tool to find DLL dependents. class ctypes. OleDLL ( name , mode = DEFAULT_MODE , handle = None , use_errno = False , use_last_error = False , winmode = None ) ¶ Instances of this class represent loaded shared libraries, functions in these libraries use the stdcall calling convention, and are assumed to return the windows specific HRESULT code. HRESULT values contain information specifying whether the function call failed or succeeded, together with additional error code. If the return value signals a failure, an OSError is automatically raised. Availability : Windows Changed in version 3.3: WindowsError used to be raised, which is now an alias of OSError . Changed in version 3.12: The name parameter can now be a path-like object . class ctypes. WinDLL ( name , mode = DEFAULT_MODE , handle = None , use_errno = False , use_last_error = False , winmode = None ) ¶ Instances of this class represent loaded shared libraries, functions in these libraries use the stdcall calling convention, and are assumed to return int by default. Availability : Windows Changed in version 3.12: The name parameter can now be a path-like obj | 2026-01-13T08:49:04 |
https://popcorn.forem.com/popcorn_movies/james-gunn-to-direct-next-movie-in-the-super-family-at-dc-studios-after-superman-success-3i76 | James Gunn to Direct ‘Next Movie in the Super-Family' at DC Studios After ‘Superman' Success - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close 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 Movie News Posted on Aug 8, 2025 James Gunn to Direct ‘Next Movie in the Super-Family' at DC Studios After ‘Superman' Success # marketing # filmindustry # distribution # studios James Gunn to Direct 'Superman' Sequel: 'Next Movie in Super-Family'James Gunn to Direct 'Superman' Sequel: 'Next Movie in Super-Family' James Gunn will write and direct the "next movie in the Super-Family" after the success of "Superman" this summer. variety.com 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 Movie News Follow Joined Jun 22, 2025 More from Movie News CinemaSins: Everything Wrong With Austin Powers in Goldmember in 19 Minutes Or Less # movies # reviews # analysis # marketing Mr Sunday Movies: The Judge Dredd Duology - Caravan Of Garbage # movies # reviews # analysis # marketing CinemaSins: Everything Wrong With Weapons In 21 Minutes Or Less # movies # reviews # analysis # marketing 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:04 |
https://gg.forem.com/t/pcgaming | Pcgaming - Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close # pcgaming Follow Hide High-end rigs, mods, and raw power Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Forty Hours on Arrakis: A Dune Awakening Experience Evan Lausier Evan Lausier Evan Lausier Follow Jan 5 Forty Hours on Arrakis: A Dune Awakening Experience # steam # pcgaming # mmorpg # openworld Comments Add Comment 4 min read 🍋 LemonLoader — Real-World Android Mod Loader for Unity Games Miller Miller Miller Follow Dec 19 '25 🍋 LemonLoader — Real-World Android Mod Loader for Unity Games # gamedev # modding # pcgaming # steam Comments 1 comment 2 min read 7 Hard Truths I Learned Running a Gaming Community for 13 Years Howard Howard Howard Follow Dec 9 '25 7 Hard Truths I Learned Running a Gaming Community for 13 Years # community # clans # pcgaming # advice 30 reactions Comments 3 comments 4 min read 🚀 Launching Market Tycoon: A Casual Supermarket Management Game! seagames seagames seagames Follow Dec 6 '25 🚀 Launching Market Tycoon: A Casual Supermarket Management Game! # indie # gamedev # pcgaming # playstation 48 reactions Comments 1 comment 3 min read 💥 When Your Game Plays YOU: The Algorithm Behind Marvel Rivals Faisal Mujahid Faisal Mujahid Faisal Mujahid Follow Dec 9 '25 💥 When Your Game Plays YOU: The Algorithm Behind Marvel Rivals # gamedev # pcgaming # fps # battleroyale 2 reactions Comments 1 comment 1 min read 🚇 Metro — The Only Series That Made Me Afraid of Breathing Faisal Mujahid Faisal Mujahid Faisal Mujahid Follow Dec 3 '25 🚇 Metro — The Only Series That Made Me Afraid of Breathing # indie # pcgaming # gamedev # playstation 1 reaction Comments 2 comments 1 min read One Year of Building My Untitled Horror Inspired OS Game STG STG STG Follow Nov 19 '25 One Year of Building My Untitled Horror Inspired OS Game # indie # gamedev # pcgaming # modding 4 reactions Comments 10 comments 2 min read Messenger: A Tiny Planet, Big Heart — Why This Browser Game Is a Hidden Gem Engineer Robin 🎭 Engineer Robin 🎭 Engineer Robin 🎭 Follow Nov 22 '25 Messenger: A Tiny Planet, Big Heart — Why This Browser Game Is a Hidden Gem # gamedev # pcgaming # vrgaming # xbox 6 reactions Comments Add Comment 2 min read IGN: Vampire: The Masquerade - Bloodlines 2: First 12 Minutes of Gameplay Gaming News Gaming News Gaming News Follow Oct 17 '25 IGN: Vampire: The Masquerade - Bloodlines 2: First 12 Minutes of Gameplay # pcgaming # playstation Comments Add Comment 1 min read IGN: Code Vein 2 Preview: New Moon, Same Blood Gaming News Gaming News Gaming News Follow Oct 13 '25 IGN: Code Vein 2 Preview: New Moon, Same Blood # pcgaming Comments Add Comment 1 min read Rewind This: How Prince of Persia Made Breaking the Rules Look Like Art Faisal Mujahid Faisal Mujahid Faisal Mujahid Follow Nov 17 '25 Rewind This: How Prince of Persia Made Breaking the Rules Look Like Art # gamedev # pcgaming # playstation # xbox 1 reaction Comments 1 comment 1 min read GameSpot: Why The Warriors is Rockstars BEST (non-GTA/Red Dead) Game Gaming News Gaming News Gaming News Follow Oct 11 '25 GameSpot: Why The Warriors is Rockstars BEST (non-GTA/Red Dead) Game # pcgaming # retrogaming Comments Add Comment 1 min read IGN: Call of Duty: Warzone & Black Ops 6 - Official 'The Haunting x Jason' Trailer Gaming News Gaming News Gaming News Follow Oct 12 '25 IGN: Call of Duty: Warzone & Black Ops 6 - Official 'The Haunting x Jason' Trailer # pcgaming # xbox Comments Add Comment 1 min read IGN: Absolum Review Gaming News Gaming News Gaming News Follow Oct 9 '25 IGN: Absolum Review # pcgaming # nintendoswitch # indie # playstation Comments Add Comment 1 min read The Game Theorists: Game Theory: How DEADLY Is Donkey Kong's Punch? Gaming News Gaming News Gaming News Follow Oct 8 '25 The Game Theorists: Game Theory: How DEADLY Is Donkey Kong's Punch? # nintendo # nintendoswitch # retrogaming # pcgaming Comments Add Comment 1 min read IGN: Megabonk - Quick Review Gaming News Gaming News Gaming News Follow Oct 7 '25 IGN: Megabonk - Quick Review # pcgaming # indie # steam Comments Add Comment 1 min read GameSpot: How Can EA Save Its Reputation? Gaming News Gaming News Gaming News Follow Oct 6 '25 GameSpot: How Can EA Save Its Reputation? # gamedev # pcgaming Comments Add Comment 1 min read Wolverine PS5 Game: Insomniac’s Marvel Hit Sanjay Naker Sanjay Naker Sanjay Naker Follow Oct 7 '25 Wolverine PS5 Game: Insomniac’s Marvel Hit # gamedev # pcgaming # indie # playstation Comments Add Comment 2 min read GameSpot: Heck of a Week to Start a Gaming News Show | Kurt & Lucy Gotcha Covered Gaming News Gaming News Gaming News Follow Oct 6 '25 GameSpot: Heck of a Week to Start a Gaming News Show | Kurt & Lucy Gotcha Covered # pcgaming # steam # xbox # retrogaming Comments Add Comment 1 min read IGN: Assassin's Creed Mirage - Official Valley of Memory Update Overview Gaming News Gaming News Gaming News Follow Oct 7 '25 IGN: Assassin's Creed Mirage - Official Valley of Memory Update Overview # pcgaming # playstation # xbox # steam Comments Add Comment 1 min read IGN: Assassin's Creed Mirage - Official Valley of Memory Update Teaser Trailer Gaming News Gaming News Gaming News Follow Oct 6 '25 IGN: Assassin's Creed Mirage - Official Valley of Memory Update Teaser Trailer # pcgaming Comments Add Comment 1 min read IGN: Bye Sweet Carole - Official Launch Trailer Gaming News Gaming News Gaming News Follow Oct 10 '25 IGN: Bye Sweet Carole - Official Launch Trailer # indie # pcgaming # playstation # xbox Comments Add Comment 1 min read IGN: Call of Duty: Black Ops 6 - Official Season 6 Multiplayer Maps Trailer Gaming News Gaming News Gaming News Follow Oct 9 '25 IGN: Call of Duty: Black Ops 6 - Official Season 6 Multiplayer Maps Trailer # pcgaming Comments Add Comment 1 min read IGN: Netflix's Splinter Cell: Deathwatch Review Gaming News Gaming News Gaming News Follow Oct 14 '25 IGN: Netflix's Splinter Cell: Deathwatch Review # pcgaming # xbox # playstation 5 reactions Comments Add Comment 1 min read The $2 Billion Bet: Inside GTA VI’s Record-Breaking Budget creativeambition creativeambition creativeambition Follow Oct 28 '25 The $2 Billion Bet: Inside GTA VI’s Record-Breaking Budget # gamedev # gtavi # openworld # pcgaming 11 reactions Comments 9 comments 3 min read loading... trending guides/resources Rewind This: How Prince of Persia Made Breaking the Rules Look Like Art 💥 When Your Game Plays YOU: The Algorithm Behind Marvel Rivals 🚇 Metro — The Only Series That Made Me Afraid of Breathing 🍋 LemonLoader — Real-World Android Mod Loader for Unity Games Forty Hours on Arrakis: A Dune Awakening Experience Messenger: A Tiny Planet, Big Heart — Why This Browser Game Is a Hidden Gem One Year of Building My Untitled Horror Inspired OS Game 7 Hard Truths I Learned Running a Gaming Community for 13 Years 🚀 Launching Market Tycoon: A Casual Supermarket Management Game! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:49:04 |
https://future.forem.com/privacy#2-personal-information-we-collect | Privacy Policy - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:04 |
https://www.papaparse.com/ | Papa Parse - Powerful CSV Parser for JavaScript Papa Parse The powerful, in-browser CSV parser for big boys and girls Download Demo Documentation // Parse CSV string var data = Papa.parse(csv); // Convert back to CSV var csv = Papa.unparse(data); // Parse local CSV file Papa.parse(file, { complete: function(results) { console.log("Finished:", results.data); } }); // Stream big file in worker thread Papa.parse(bigFile, { worker: true, step: function(results) { console.log("Row:", results.data); } }); Demo Docs FAQ Papa Parse 5 GitHub Help Version 5.0 Features Now the fastest JavaScript CSV parser for the browser The world's first multi-threaded CSV parser for the browser Papa can handle files gigabytes in size without crashing Use Papa when performance, privacy, and correctness matter to you Papa alleviates privacy concerns related to uploading files Malformed CSV is handled gracefully with a detailed error report CSV→JSON and JSON→CSV Auto-detect delimiter Open local files Download remote files Stream local and remote files Multi-threaded Header row support Type conversion Skip commented lines Fast mode Graceful error handling Optional sprinkle of jQuery GitHub Documentation People Papa SmartyStreets verifies addresses, many of which are in CSV files. Papa Parse can process huge files in the browser. "We rapidly built an awesome client-side file processor with Papa Parse." MetaReader helps you see your data from a meta level before you start detailed analysis. "Papa Parse made it very easy to load and ready user CSV files in the browser on the client side." EpiML is an agent-based mathematical model for the web, still in its early stages of development. "Papa makes it so easy to use CSV, which is good for scientists." Add your link (it's free) CSV Parsing "Isn't parsing CSV just String.split(',') ?" Heavens, no. Papa does it right. Just pass in the CSV string with an optional configuration . var results = Papa.parse(csvString, config ); /* results = { data: [ ... ], // parsed data errors: [ ... ], // errors encountered meta: { ... } // extra parse info } */ Delimiter Detection "But I don't know the delimiter..." That's okay. Papa will scan the first few rows to find the right delimiter. var results = Papa.parse(csvString); console.log(results.meta.delimiter); // "\t" Local Files "Great, but I have a file to parse." Then give Papa a File instead of a string. Since file parsing is asynchronous, don't forget a callback. Papa.parse(fileInput.files[0], { complete: function(results) { console.log(results); } }); Remote Files "No—I mean, the file isn't on my computer." Oh, well then just pass in the URL and—of course—a callback. Papa.parse("http://example.com/file.csv", { download: true, complete: function(results) { console.log(results); } }); Streaming "Did I mention the file is huge?" That's what streaming is for. Specify a step callback to receive the results row-by-row. This way, you won't load the whole file into memory and crash the browser. Papa.parse("http://example.com/big.csv", { download: true, step: function(row) { console.log("Row:", row.data); }, complete: function() { console.log("All done!"); } }); Multi-Threading "Lovely. Now my web page locked up." That happens when a long-running script is executing in the same thread as the page. Use a Worker thread by specifying worker: true . It may take slightly longer, but your page will stay reactive. Papa.parse(bigFile, { worker: true, step: function(row) { console.log("Row:", row.data); }, complete: function() { console.log("All done!"); } }); Header Row "Great! Now I want data keyed by field name." If you tell Papa there is a header row, each row will be organized by field name instead of index. // Key data by field name instead of index/position var results = Papa.parse(csv, { header: true }); Type Conversion "Hey, these numbers are parsed as strings." Everything is parsed as strings. If you want numbers and booleans, you can enable dynamic typing to do the conversion for you. // Converts numeric/boolean data var results = Papa.parse(csv, { dynamicTyping: true }); Comments "I forgot to mention: my CSV files have comments in them." Okay, first off: that's really weird. But fortunately, you can skip those lines... just specify the comment string. // Mostly found in academia, some CSV files // may have commented lines in them var results = Papa.parse(csv, { comments: "#" }); Error Handling "Aw, shoot. Errors." Papa handles errors pretty well. The CSV standard is somewhat loose ambiguous, so Papa is designed for edge cases. For example, mismatched fields won't break parsing. // Example error: { type: "FieldMismatch", code: "TooManyFields", message: "Expected 3 fields, but parsed 4", row: 1 } jQuery Plugin "Can I use Papa with jQuery?" Sure, but it's not required. You can use jQuery to select file input elements and then parse their files. Papa exposes its file parsing API as a jQuery plugin only when jQuery is defined. Papa Parse has no dependencies . $("input[type=file]").parse({ config: { complete: function(results, file) { console.log("This file done:", file, results); } }, complete: function() { console.log("All files done!"); } }); JSON to CSV "Last thing: what about converting JSON to CSV?" Call unparse() instead of parse() , passing in your array of arrays or array of objects. Papa will figure it out. // Output is a properly-formatted CSV string. // See the docs for more configurability. var csv = Papa.unparse(yourData); Who's Your Papa? Lil' Papa (minified) for production use Fat Papa (un-minified) for development npm $ npm install papaparse bower $ bower install papaparse GitHub Demo Documentation Make Your Papa Proud Star and shout if you love #PapaParse --> P Papa Parse by Matt Holt © 2013-2019 Learn Demo Documentation FAQ Project Donate GitHub Share Download Latest (master) Lil' Papa Fat Papa Community Twitter Stack Overflow | 2026-01-13T08:49:04 |
https://mail.python.org/mailman/listinfo/psf-community | Mailman 3 Info | psf-community@python.org - python.org Toggle navigation Postorius Sign In Sign Up Lists Archives Sign In Sign Up PSF-Community psf-community@python.org Summary A mailing list for the PSF Community The purpose of the psf-community mailing list is to provide an environment where pythonistas can communicate with a large audience, share experiences, launch projects, and/or discuss their Python & OSS interests. This community mailing list will have public archives, accessible to everyone. In order to nurture a friendly environment, we ask that you familiarize yourself with our Code of Conduct and be kind and respectful of one another. Mailing list discussions can get intense and tend to spike in volume from time to time. If you are caught in a heated discussion, keep the discussion focused on issues rather than the personalities involved. A good approach is to wait overnight to send emotional responses to messages. Keep in mind that a large audience will see your posts. This may include your current or future employers. Take care in what you write. Remember, this mailing list is publicly archived, and that your words will be stored publicly for a very long time. To contact the list owners, use the following email address: psf-community-owner@python.org Archives Archives Subscription / Unsubscription To subscribe or unsubscribe from this list, please sign in first. If you have not previously signed in, you may need to set up an account with the appropriate email address. Sign In Postorius Documentation • GNU Mailman • Postorius Version 1.3.13 | 2026-01-13T08:49:04 |
https://rsionnach.github.io/nthlayer/getting-started/first-service/#complete-service-example | Your First Service - NthLayer Documentation Skip to content NthLayer Documentation Your First Service Initializing search rsionnach/nthlayer NthLayer Documentation rsionnach/nthlayer Home Live Demo Getting Started Getting Started Installation Quick Start Interactive Setup Your First Service Your First Service Table of contents Minimal Service Complete Service Example Service Tiers Service Types Dependencies Generate and Apply Next Steps Adoption Path Generate Generate nthlayer apply nthlayer init Loki Alerts Technology Templates Validate Validate Overview Contract Verification Policy Validation Metadata Validation PromQL Linting Protect Protect Overview Deployment Gates Drift Detection SLO Portfolio Integrations Integrations CI/CD Pipelines Prometheus Mimir/Cortex Grafana PagerDuty PagerDuty Safety Concepts Concepts Reliability Shift Left Service Tiers Contracts & Assumptions Deployment Gates Service Specs SLOs & Error Budgets Reference Reference Service YAML Schema Technology Templates CLI Reference Environment Management Architecture Table of contents Minimal Service Complete Service Example Service Tiers Service Types Dependencies Generate and Apply Next Steps Your First Service ¶ Learn how to create a complete service specification. Minimal Service ¶ The simplest service spec: name : my-api tier : standard type : api This generates default SLOs for a standard API (99.9% availability, 500ms p99 latency). Complete Service Example ¶ name : payment-api team : payments tier : critical # 1=critical, 2=standard, 3=low type : api # api, worker, stream # Technology dependencies dependencies : - postgresql - redis # Custom SLO overrides resources : - kind : SLO name : availability spec : objective : 99.95 window : 30d indicator : type : availability query : | sum(rate(http_requests_total{service="payment-api",status!~"5.."}[5m])) / sum(rate(http_requests_total{service="payment-api"}[5m])) - kind : SLO name : latency-p99 spec : objective : 99.0 window : 30d threshold_ms : 200 indicator : type : latency percentile : 99 # PagerDuty configuration - kind : PagerDuty name : alerting spec : urgency : high auto_create : true Service Tiers ¶ Tier Availability Latency (p99) Escalation 1 (Critical) 99.95% 200ms 5 min 2 (Standard) 99.9% 500ms 15 min 3 (Low) 99.5% 1000ms 30 min Service Types ¶ Type Description Key Metrics api HTTP/REST services Request rate, latency, error rate worker Background jobs Job throughput, duration, failure rate stream Event processors Messages/sec, lag, processing time Dependencies ¶ NthLayer generates monitoring for these technologies: Databases Message Queues Proxies Infrastructure postgresql - Connections, replication, locks mysql - Connections, queries, replication mongodb - Connections, operations, replication redis - Memory, connections, hit rate elasticsearch - Cluster health, indexing, search kafka - Consumer lag, partitions, throughput rabbitmq - Queue depth, consumers, rates nats - Connections, messages, subscriptions pulsar - Throughput, backlog, storage nginx - Requests, connections, upstream haproxy - Backend health, response time traefik - Requests, entrypoints kubernetes - Pod health, resources etcd - Leader, proposals, DB size consul - Health checks, services Generate and Apply ¶ # Preview what will be generated nthlayer plan payment-api.yaml # Generate all configs nthlayer apply payment-api.yaml # Push dashboard to Grafana (if configured) nthlayer apply payment-api.yaml --push Next Steps ¶ nthlayer apply - Full apply options Technologies - All 18 templates Service YAML Schema - Complete schema reference Back to top Made with Material for MkDocs | 2026-01-13T08:49:04 |
https://www.python.org/download/alternatives#top | Alternative Python implementations | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Alternative Python implementations This site hosts the "traditional" implementation of Python (nicknamed CPython). A number of alternative implementations are available as well, namely PyPy (a fast implementation of Python with a JIT compiler) IronPython (Python running on .NET) MicroPython (Python running on microcontrollers and in the web browser ) Stackless Python (a branch of CPython supporting microthreads) Jython (Python running on the Java Virtual Machine) GraalPy (embeddable Python runtime for Java) Other parties have repackaged CPython. These re-packagings often include more libraries or are specialized for a particular application: Anaconda Python (a full Python distribution for data management, analysis and visualization of large data sets) ActiveState ActivePython (commercial and community versions, including scientific computing modules) Nuitka (a compiler that packages user code with CPython into a static binary for improved performance and IP protection) pyodide (a Python distribution for the browser and Node.js based on WebAssembly) WinPython (a portable scientific Python distribution for Windows) Python(x, y) (Scientific-oriented distribution based on Qt and Spyder) Conceptive Python SDK (targets business, desktop and database applications) PyIMSL Studio (a commercial distribution for numerical analysis – free for non-commercial use) eGenix PyRun (a portable Python runtime, complete with stdlib, frozen into a single 3.5MB - 13MB executable file) If you want to host and run Python in the cloud, these implementations may be right for you: PythonAnywhere (freemium hosted Python installation which lets you run Python in the browser, e.g. for tutorials, showcases) The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://docs.python.org/3/license.html#cookie-management | 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:49:04 |
https://www.python.org/psf/membership-faq | PSF Membership Types & FAQ | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF Membership Types & FAQ The mission of the Python Software Foundation is to promote, protect, and advance the Python programming language, and to support and facilitate the growth of the international community of Python programmers. —from the Mission Statement page What does it mean to be a member of the PSF? What membership classes are there? Who is allowed to vote? Why am I a Basic Member even though I’m a Supporting/Contributing/Fellow Member? How does a person become a PSF Fellow? What does the PSF do? How can I ask other questions? What does it mean to be a member of the PSF? Being part of the PSF means being part of the Python community. In 2014, we changed the bylaws to make the PSF an open membership organization, so that everyone who uses and supports Python can join. For those who wish to participate more, we have classes of membership that include voting rights for those who contribute time, work, and money to the foundation. What membership classes are there? There are four classes of members: Basic Members, Supporting Members, Contributing Members and Fellows. Basic Members Basic members are individuals or entities who are part of the Python language community and who have decided to declare their support for Python and agree to the community Code of Conduct. There is no cost to be a Basic Member. You can sign up as a basic member right here on the site . Supporting Members Supporting Members make a specific annual donation to the PSF to sustain the Foundation and support the Python community. Supporting Members are eligible to vote. You may combine Supporting Membership with any other Membership - i.e. you may sign up for Supporting Membership and also be a Basic Member, Contributing Member, or a Fellow. You can sign up as a Supporting Member here . Contributing Members Contributing Members are people who dedicate at least five hours per month volunteering on projects that advance the mission of the PSF, where the work relates to the creation or maintenance of open source software available to the public at no charge, or by organizing Python events, running infrastructure, participating in one of the PSF's working groups, etc. Contributing Members are eligible to vote. There is no cost to be a Contributing Member. For details on signing up as a Contributing Member, refer to this form . Fellows Fellows are members who have been nominated for their extraordinary efforts and impact upon Python, the community, and the broader Python ecosystem. Fellows are nominated from the broader community and elevated by a vote of the members. Fellow members are eligible to vote. More info on the nomination process is available here . Who is allowed to vote? Who is eligible: Supporting Members, Contributing Members, and Fellows are eligible for voting privileges. To vote you must be 1) eligible to vote, and then 2) affirm each year you would like to exercise your voting privileges. More information on affirming your voting status is here. Why am I a Basic Member even though I’m a Supporting/Contributing/Fellow Member? Your Basic Membership information is managed here on https://www.python.org/users/membership/edit/ . To manage your Supporting and Contributing Memberships, visit https://psfmember.org/user-information/ . This site, https://www.python.org , will list you as a Basic Member even if you are a Supporting, Contribution, or Fellowship member because the voting tiers of membership are managed on the separate, https://www.psfmember.org website. To verify your PSF Voting Eligibility you will need to use https://www.psfmember.org . If you believe you are a Supporting, Contributing, or Fellow Member but do not have an account on psfmember.org, please create an account and verify your email, then email psf-donations@python.org to get your account linked to your membership. How does a person become a PSF Fellow? To nominate someone to be a PSF Fellow member, please send your nomination to psf-fellow@python.org . More info on the nomination process is available here . The criteria for becoming a PSF Fellow are as follows: For those who have served the Python community by creating and/or maintaining various creative contributions, the following statement should be true: "[Nominated Person] has served the Python community by making available code, tests, documentation, or design, either in a Python implementation or in a Python ecosystem project, that 1) shows technical excellence, 2) is an example of software engineering principles and best practices, and 3) has achieved widespread usage or acclaim." For those who have served the Python community by coordinating, organizing, teaching, writing, and evangelizing, the following statement should be true: "[Nominated Person] has served the Python community through extraordinary efforts in organizing Python events, publicly promoting Python, and teaching and coordinating others. [Nominated Person]'s efforts have shown leadership and resulted in long-lasting and substantial gains in the number and quality of Python users, and have been widely recognized as being above and beyond normal volunteering." In all that this person does, [Nominated Person] is an example of what we aspire to be in the Python community. What does the PSF do? The majority of the PSF's work is focused on empowering and supporting people within the Python community. The PSF has active grant programs that support sprints, conferences, meetups, user groups, and Python development efforts all over the world. In addition, the PSF underwrites and runs PyCon US, the primary Python community conference. The PSF serves as a primary point of contact for organizations seeking to work with Python, to support Python, or to sponsor Python development. The PSF provides a structure by which work, donations and sponsorships can be coordinated worldwide. The PSF also holds and protects the intellectual property associated with Python and the Python community - like the word "Python," the two-snakes logo, and the terms "PyLadies" and "PyCon." We make sure that these terms are used appropriately and only for the benefit of the Python community. You can learn more here or in our latest Annual Report . How can I ask other questions? Please send questions to psf-donations@python.org . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://www.google.com | Google 검색 이미지 지도 Play YouTube 뉴스 Gmail 드라이브 더보기 » 웹 기록 | 설정 | 로그인 고급검색 광고 비즈니스 솔루션 Google 정보 Google.co.kr © 2026 - 개인정보처리방침 - 약관 | 2026-01-13T08:49:04 |
https://dev.to/t/programming/page/78 | Programming Page 78 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 75 76 77 78 79 80 81 82 83 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How I Connected Claude Desktop to Notion using MCP (Open Source & Cloud-Hosted) Piskun Lab Piskun Lab Piskun Lab Follow Dec 15 '25 How I Connected Claude Desktop to Notion using MCP (Open Source & Cloud-Hosted) # programming # mcp # ai # tutorial 2 reactions Comments Add Comment 2 min read Testability vs. Automatability: Why Most Automation Efforts Fail Before They Begin tanvi Mittal tanvi Mittal tanvi Mittal Follow for AI and QA Leaders Dec 18 '25 Testability vs. Automatability: Why Most Automation Efforts Fail Before They Begin # webdev # ai # programming # testing 5 reactions Comments Add Comment 3 min read Coding Without Pressure: How Slowing Down Helped Me Learn Faster Hadil Ben Abdallah Hadil Ben Abdallah Hadil Ben Abdallah Follow Dec 25 '25 Coding Without Pressure: How Slowing Down Helped Me Learn Faster # webdev # productivity # programming # codenewbie 244 reactions Comments 83 comments 3 min read This Open-Source LLM Gateway is 54x Faster Than LiteLLM (Here's Why) Debby McKinney Debby McKinney Debby McKinney Follow Jan 8 This Open-Source LLM Gateway is 54x Faster Than LiteLLM (Here's Why) # opensource # ai # programming # chatgpt 11 reactions Comments 1 comment 5 min read Mock Data API That Actually Understands Foreign Keys Divan Divan Divan Follow Dec 15 '25 Mock Data API That Actually Understands Foreign Keys # webdev # programming # api # sideprojects Comments Add Comment 4 min read Common Mistakes Beginners Make in JavaScript (I Made Them Too) Md Akash Mia Md Akash Mia Md Akash Mia Follow Dec 21 '25 Common Mistakes Beginners Make in JavaScript (I Made Them Too) # webdev # programming # javascript # php Comments Add Comment 1 min read What Makes a Good Browser-Based Platformer? Lessons from Modern HTML5 Games gamh5games gamh5games gamh5games Follow Dec 15 '25 What Makes a Good Browser-Based Platformer? Lessons from Modern HTML5 Games # webdev # programming # ai # javascript 5 reactions Comments 1 comment 2 min read React in Crisis? Why the "React2Shell" Vulnerability Has Developers Scrambling (and What It Means for Your App) Amol Yadav Amol Yadav Amol Yadav Follow Dec 15 '25 React in Crisis? Why the "React2Shell" Vulnerability Has Developers Scrambling (and What It Means for Your App) # react # devbugsmash # webdev # programming Comments Add Comment 2 min read I Stopped Chasing New Frameworks. My Code Got Better Gelo Gelo Gelo Follow Jan 5 I Stopped Chasing New Frameworks. My Code Got Better # programming # learning # career # softwaredevelopment 27 reactions Comments 1 comment 2 min read Code Smell 316 - Nitpicking Maxi Contieri Maxi Contieri Maxi Contieri Follow Dec 16 '25 Code Smell 316 - Nitpicking # webdev # programming # beginners # tutorial 1 reaction Comments Add Comment 8 min read The "Tutorial Gap": What I Learned Moving from Sample Datasets to Real-World AI Aditya Mishra Aditya Mishra Aditya Mishra Follow Dec 29 '25 The "Tutorial Gap": What I Learned Moving from Sample Datasets to Real-World AI # webdev # programming # ai # javascript Comments Add Comment 1 min read 7 Essential Tools to Supercharge Your Python Development Workflow James Miller James Miller James Miller Follow Dec 16 '25 7 Essential Tools to Supercharge Your Python Development Workflow # python # tooling # programming # webdev Comments Add Comment 5 min read Cracking the Code: AI Data Storage in Depth Malik Abualzait Malik Abualzait Malik Abualzait Follow Dec 16 '25 Cracking the Code: AI Data Storage in Depth # ai # tech # programming # tutorial Comments Add Comment 3 min read "ElysiaJS" for AI Agents? New SDK for Bun Acauã Rangel Acauã Rangel Acauã Rangel Follow Dec 15 '25 "ElysiaJS" for AI Agents? New SDK for Bun # ai # bunjs # agents # programming Comments Add Comment 1 min read Day 69: Python Conway's Game of Life - Simulate One Step of Cellular Automata with Neighbor Scanning Magic Shahrouz Nikseresht Shahrouz Nikseresht Shahrouz Nikseresht Follow Dec 19 '25 Day 69: Python Conway's Game of Life - Simulate One Step of Cellular Automata with Neighbor Scanning Magic # challenge # python # algorithms # programming 1 reaction Comments Add Comment 3 min read The Hydra Encoding-Decoding Toolbox zayan zakir zayan zakir zayan zakir Follow Dec 16 '25 The Hydra Encoding-Decoding Toolbox # webdev # programming # ai # javascript Comments Add Comment 2 min read C Programming Tutorial for Beginners | Learn C from Scratch Code Practice Code Practice Code Practice Follow Dec 30 '25 C Programming Tutorial for Beginners | Learn C from Scratch # c # coding # programming # computerscience Comments Add Comment 4 min read About the author: This blog was written by a Python enthusiast who started their coding journey just like you. Connect w… Kavi Kr Kavi Kr Kavi Kr Follow Dec 16 '25 About the author: This blog was written by a Python enthusiast who started their coding journey just like you. Connect w… # beginners # programming # python Comments Add Comment 1 min read Optimizing JSON for LLMs Matt Lewandowski Matt Lewandowski Matt Lewandowski Follow Jan 8 Optimizing JSON for LLMs # webdev # programming # ai # beginners 66 reactions Comments 7 comments 6 min read Five Projects, Carefully Unhinged and Fully Deployed TROJAN TROJAN TROJAN Follow Jan 3 Five Projects, Carefully Unhinged and Fully Deployed # webdev # programming # ai # hireme 26 reactions Comments 17 comments 1 min read 🎀 The 80/20 Rule of Learning Programming TheBitForge TheBitForge TheBitForge Follow Jan 6 🎀 The 80/20 Rule of Learning Programming # webdev # programming # javascript # react 45 reactions Comments 2 comments 42 min read WebSocket Mock Server with a Beautiful Terminal UI abidibo abidibo abidibo Follow Jan 8 WebSocket Mock Server with a Beautiful Terminal UI # node # programming # typescript # webdev Comments Add Comment 5 min read How I Ship Features 10x Faster Than Most Developers (And Why Speed Is My Only Competitive Advantage) Angelo Asante Angelo Asante Angelo Asante Follow Dec 15 '25 How I Ship Features 10x Faster Than Most Developers (And Why Speed Is My Only Competitive Advantage) # webdev # programming # ai # beginners 5 reactions Comments Add Comment 10 min read Looking for Collaborators & Feedback: Building a Free, Accessible HRT Journey Tracker for the Trans Community codebunny20 codebunny20 codebunny20 Follow Jan 5 Looking for Collaborators & Feedback: Building a Free, Accessible HRT Journey Tracker for the Trans Community # programming # beginners # python # learning Comments Add Comment 2 min read Mastering Unix Domain Sockets in Go: Fast, Local IPC for Your Apps Jones Charles Jones Charles Jones Charles Follow Dec 16 '25 Mastering Unix Domain Sockets in Go: Fast, Local IPC for Your Apps # go # webdev # programming # networking Comments Add Comment 7 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Faskrishnapravin%2Ffor-loop-vs-map-for-making-multiple-api-calls-3lhd&title=for%20loop%20vs%20.map%28%29%20for%20making%20multiple%20API%20calls&summary=Comparison%20of%20for%2C%20for...in%2C%20for...of%20loop%20vs%20.map%28%29%20for%20making%20multiple%20API%20calls%20and%20the%20reason%20why%20map%20is%20faster.&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:04 |
https://dev.to/t/testing | Testing - 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 Testing Follow Hide Find those bugs before your users do! 🐛 Create Post Older #testing posts 1 2 3 4 5 6 7 8 9 … 75 … 481 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu SLMs, LLMs and a Devious Logic Puzzle Test Ben Santora Ben Santora Ben Santora Follow Jan 12 SLMs, LLMs and a Devious Logic Puzzle Test # llm # performance # testing 5 reactions Comments Add Comment 5 min read Observing Behavioral Anomalies in Web Applications Beyond Signature Scanners 0x7b 0x7b 0x7b Follow Jan 12 Observing Behavioral Anomalies in Web Applications Beyond Signature Scanners # monitoring # performance # security # testing Comments Add Comment 1 min read How to handle drag and drop with Cypress in Workflow Builder Daniil Daniil Daniil Follow Jan 13 How to handle drag and drop with Cypress in Workflow Builder # testing # cypress # javascript # ai Comments Add Comment 2 min read Case Study (Day 0): Testing a Topical Authority Burst Strategy on a Brand-New Site Topical HQ Topical HQ Topical HQ Follow Jan 13 Case Study (Day 0): Testing a Topical Authority Burst Strategy on a Brand-New Site # devjournal # marketing # startup # testing 4 reactions Comments Add Comment 2 min read TWD Tip: Stub Auth0 Hooks and Mock React Modules Kevin Julián Martínez Escobar Kevin Julián Martínez Escobar Kevin Julián Martínez Escobar Follow Jan 12 TWD Tip: Stub Auth0 Hooks and Mock React Modules # webdev # testing # react # twd Comments Add Comment 3 min read Package Updates Are Investments, Not Hygiene Tasks Steven Stuart Steven Stuart Steven Stuart Follow Jan 12 Package Updates Are Investments, Not Hygiene Tasks # leadership # softwaredevelopment # testing Comments Add Comment 8 min read When Tests Keep Passing, but Design Stops Moving Felix Asher Felix Asher Felix Asher Follow Jan 12 When Tests Keep Passing, but Design Stops Moving # tdd # ai # testing # softwareengineering Comments Add Comment 3 min read Testing in the Age of AI Agents: How I Kept QA from Collapsing wintrover wintrover wintrover Follow Jan 12 Testing in the Age of AI Agents: How I Kept QA from Collapsing # testing # qa # automation # tdd Comments Add Comment 4 min read Integration tests in Node.js with Mocha/Chai Lucas Pereira de Souza Lucas Pereira de Souza Lucas Pereira de Souza Follow Jan 12 Integration tests in Node.js with Mocha/Chai # api # javascript # node # testing Comments Add Comment 6 min read From Manual Testing to AI Pipelines: Lessons That Never Changed in My QA Career Adnan Arif Adnan Arif Adnan Arif Follow Jan 12 From Manual Testing to AI Pipelines: Lessons That Never Changed in My QA Career # ai # machinelearning # testing Comments Add Comment 4 min read Testes de integração em Node.js com Mocha/Chai Lucas Pereira de Souza Lucas Pereira de Souza Lucas Pereira de Souza Follow Jan 12 Testes de integração em Node.js com Mocha/Chai # api # javascript # node # testing Comments Add Comment 7 min read [Go] Useful Packages from Go's Internal Source Code: go-internal Evan Lin Evan Lin Evan Lin Follow Jan 11 [Go] Useful Packages from Go's Internal Source Code: go-internal # learning # testing # tooling # go Comments Add Comment 3 min read How I stopped Claude Code from hallucinating on Day 4 (The "Spec-Driven" Workflow) Samarth Hathwar Samarth Hathwar Samarth Hathwar Follow Jan 12 How I stopped Claude Code from hallucinating on Day 4 (The "Spec-Driven" Workflow) # productivity # ai # claudecode # testing Comments Add Comment 3 min read How to Generate Test Data for PostgreSQL (2 Methods) DDLTODATA DDLTODATA DDLTODATA Follow Jan 11 How to Generate Test Data for PostgreSQL (2 Methods) # postgres # testing # data # tutorial Comments Add Comment 3 min read TWD 1.4.x is out – focused on Developer Experience Kevin Julián Martínez Escobar Kevin Julián Martínez Escobar Kevin Julián Martínez Escobar Follow Jan 11 TWD 1.4.x is out – focused on Developer Experience # webdev # testing # twd Comments Add Comment 1 min read [Golang] Testing Twitter Authentication and Building a Timeline Project Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang] Testing Twitter Authentication and Building a Timeline Project # testing # api # tutorial # go Comments Add Comment 1 min read I asked devs to crash my App. Here's what happened in the first 24h (DDoS, Billing Limits & Error 1101) Elias Oliveira Elias Oliveira Elias Oliveira Follow Jan 10 I asked devs to crash my App. Here's what happened in the first 24h (DDoS, Billing Limits & Error 1101) # showdev # security # testing # devops Comments Add Comment 2 min read Vibe Coding vs AI-Driven Development: The Contracts Problem (and GS-TDD) Dennis Schmock Dennis Schmock Dennis Schmock Follow Jan 9 Vibe Coding vs AI-Driven Development: The Contracts Problem (and GS-TDD) # ai # testing # tdd # reliability Comments Add Comment 4 min read Testes de Interface com Playwright e MCP no Windsurf Victor Geruso Gomes Victor Geruso Gomes Victor Geruso Gomes Follow Jan 9 Testes de Interface com Playwright e MCP no Windsurf # webdev # ai # testing # ui Comments Add Comment 3 min read Try crash my app! I built a Link Shortener on the Edge. Can you help me crash it? (Live Dashboard) Elias Oliveira Elias Oliveira Elias Oliveira Follow Jan 9 Try crash my app! I built a Link Shortener on the Edge. Can you help me crash it? (Live Dashboard) # showdev # architecture # performance # testing Comments Add Comment 1 min read P2 - AgentEvolver 的self-question 部分代码精读 Zhaopeng Xuan Zhaopeng Xuan Zhaopeng Xuan Follow Jan 9 P2 - AgentEvolver 的self-question 部分代码精读 # agents # ai # llm # testing Comments Add Comment 1 min read Why OWASP-Aligned Testing Alone Isn’t Enough and How ZeroThreat Goes Further Jigar Shah Jigar Shah Jigar Shah Follow Jan 9 Why OWASP-Aligned Testing Alone Isn’t Enough and How ZeroThreat Goes Further # devops # security # testing Comments Add Comment 4 min read Testing Recovery: Proving Your App Helps People Stabilize CrisisCore-Systems CrisisCore-Systems CrisisCore-Systems Follow Jan 8 Testing Recovery: Proving Your App Helps People Stabilize # testing # a11y # healthcare # react Comments Add Comment 10 min read Testing Database Logic: What to Test, What to Skip, and Why It Matters CodeCraft Diary CodeCraft Diary CodeCraft Diary Follow Jan 6 Testing Database Logic: What to Test, What to Skip, and Why It Matters # programming # php # testing # development Comments Add Comment 4 min read Test Your Tests: Does Your Crisis Simulation Match Reality? CrisisCore-Systems CrisisCore-Systems CrisisCore-Systems Follow Jan 7 Test Your Tests: Does Your Crisis Simulation Match Reality? # testing # a11y # healthcare # react Comments Add Comment 10 min read loading... trending guides/resources I built my own S3 for $5/mo Shared Hosting (because no one else did) Updating to Jest 30 is Frustrating (it's JSDOM) Unit Tests: The Greatest Lie We Tell Ourselves? Playwright MCP Servers Explained: Automation and Testing Using AI in Playwright Tests Unit Testing Using Spring Boot, JUnit and Mockito Automate Microsoft MFA login using Playwright Making Pytest Beautiful: A Complete Guide to Improving Test Output (with Plugins & Examples) Crafting Effective Prompts for GenAI in Software Testing GitHub Copilot Agent Skills: Teaching AI Your Repository Patterns Stop Chatting, Start Specifying: Spec-Driven Design with Kiro IDE Maestro: A Single Framework for Mobile and Web E2E Testing ATM Hacking: From Terminator 2 Fantasy to Red Team Reality From Swagger to Tests: Building an AI-Powered API Test Generator with Python Patrol: The Flutter Testing Framework That Changes Everything 7 Best Hoppscotch Alternatives in 2025: Complete Developer's Guide to API Testing Tools It’s Time To Kill Staging: The Case for Testing in Production Agent Factory Recap: A Deep Dive into Agent Evaluation, Practical Tooling, and Multi-Agent Systems 🚀 22s to 4s: How AI Fixed Our Vitest Performance How We Catch UI Bugs Early with Visual Regression Testing 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://www.python.org/psf/records/board/minutes/ | PSF Meeting Minutes | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF Board Meeting Minutes Archive Subscribe via RSS 2025 November 12, 2025 October 22, 2025 September 10, 2025 August 13, 2025 July 16, 2025 June 20, 2025 April 9, 2025 March 12, 2025 February 12, 2025 January 8, 2025 2024 December 11, 2024 November 13, 2024 October 9, 2024 August 14, 2024 July 24, 2024 June 24, 2024 June 12, 2024 May 19, 2024 April 10, 2024 March 13, 2024 February 14, 2024 2023 December 13, 2023 November 15, 2023 October 11, 2023 October 10, 2023 September 21, 2023 August 29, 2023 June 21, 2023 May 17, 2023 March 17, 2023 February 15, 2023 January 18, 2023 2022 December 14, 2022 October 26, 2022 September 21, 2022 August 17, 2022 July 27, 2022 June 7, 2022 March 22, 2022 February 24, 2022 January 25, 2022 2021 October 26, 2021 September 23, 2021 August 24, 2021 July 22, 2021 April 28, 2021 March 31, 2021 February 24, 2021 January 27, 2021 2020 October 28, 2020 September 30, 2020 August 26, 2020 July 29, 2020 June 30, 2020 May 19, 2020 March 24, 2020 2019 September 24, 2019 August 27, 2019 July 30, 2019 March 26, 2019 January 29, 2019 2018 October 30, 2018 September 25, 2018 August 21, 2018 July 24, 2018 May 31, 2018 April 24, 2018 March 27, 2018 February 27, 2018 January 30, 2018 2017 December 18, 2017 November 20, 2017 October 16, 2017 September 26, 2017 August 22, 2017 July 25, 2017 June 26, 2017 May 10, 2017 April 3, 2017 March 3, 2017 February 6, 2017 January 13, 2017 2016 December 19, 2016 December 2, 2016 October 28, 2016 September 30, 2016 September 12, 2016 August 26, 2016 August 8, 2016 July 29, 2016 July 12, 2016 June 29, 2016 June 14, 2016 May 10, 2016 April 12, 2016 March 30, 2016 March 9, 2016 February 25, 2016 February 8, 2016 January 27, 2016 January 5, 2016 2015 December 2, 2015 November 9, 2015 October 28, 2015 October 12, 2015 September 24, 2015 August 24, 2015 August 11, 2015 July 28, 2015 July 9, 2015 June 23, 2015 June 8, 2015 May 20, 2015 May 5, 2015 April 1, 2015 February 18, 2015 January 21, 2015 January 7, 2015 2014 November 14, 2014 October 31, 2014 October 17, 2014 October 1, 2014 September 12, 2014 August 22, 2014 August 8, 2014 July 18, 2014 July 11, 2014 June 20, 2014 June 6, 2014 May 16, 2014 May 5, 2014 April 4, 2014 March 28, 2014 March 14, 2014 February 28, 2014 February 14, 2014 January 31, 2014 January 20, 2014 January 6, 2014 2013 December 6, 2013 November 15, 2013 November 1, 2013 September 27, 2013 September 13, 2013 August 30, 2013 August 16, 2013 July 26, 2013 July 12, 2013 June 28, 2013 June 14, 2013 May 31, 2013 May 10, 2013 April 26, 2013 April 12, 2013 March 29, 2013 March 5, 2013 February 20, 2013 February 6, 2013 January 16, 2013 2012 December 19, 2012 December 5, 2012 November 21, 2012 November 7, 2012 October 17, 2012 September 26, 2012 September 12, 2012 August 22, 2012 August 8, 2012 July 16, 2012 June 18, 2012 May 21, 2012 April 30, 2012 March 26, 2012 February 27, 2012 January 16, 2012 2011 December 19, 2011 November 21, 2011 October 17, 2011 September 19, 2011 August 15, 2011 July 18, 2011 June 27, 2011 May 16, 2011 April 18, 2011 March 21, 2011 February 28, 2011 January 24, 2011 2010 December 20, 2010 November 15, 2010 October 18, 2010 September 20, 2010 August 16, 2010 July 26, 2010 June 21, 2010 May 10, 2010 April 12, 2010 March 8, 2010 February 8, 2010 January 11, 2010 2009 December 21, 2009 December 14, 2009 November 9, 2009 October 12, 2009 September 14, 2009 August 10, 2009 July 13, 2009 June 8, 2009 May 11, 2009 April 13, 2009 March 27, 2009 March 12, 2009 February 9, 2009 January 12, 2009 2008 December 8, 2008 November 10, 2008 October 13, 2008 September 8, 2008 August 11, 2008 July 14, 2008 June 16, 2008 May 12, 2008 April 14, 2008 March 14, 2008 March 10, 2008 February 11, 2008 January 14, 2008 2007 December 10, 2007 November 12, 2007 October 8, 2007 September 10, 2007 August 13, 2007 July 9, 2007 June 11, 2007 May 14, 2007 April 9, 2007 March 12, 2007 February 25, 2007 February 12, 2007 January 8, 2007 2006 December 11, 2006 November 13, 2006 October 9, 2006 September 18, 2006 August 14, 2006 July 10, 2006 June 12, 2006 April 10, 2006 March 13, 2006 February 25, 2006 February 14, 2006 January 10, 2006 2005 December 13, 2005 November 8, 2005 October 11, 2005 September 13, 2005 August 9, 2005 July 12, 2005 June 14, 2005 May 10, 2005 April 12, 2005 March 24, 2005 March 8, 2005 February 8, 2005 January 11, 2005 2004 December 14, 2004 November 9, 2004 October 12, 2004 August 10, 2004 July 13, 2004 June 18, 2004 May 11, 2004 April 13, 2004 March 26, 2004 February 10, 2004 January 13, 2004 2003 December 9, 2003 November 11, 2003 October 14, 2003 September 9, 2003 August 12, 2003 June 10, 2003 May 13, 2003 April 8, 2003 March 11, 2003 February 11, 2003 January 14, 2003 2002 December 10, 2002 November 12, 2002 October 8, 2002 September 10, 2002 August 13, 2002 July 16, 2002 June 11, 2002 May 14, 2002 April 9, 2002 March 12, 2002 February 12, 2002 February 7, 2002 2001 March 8, 2001 March 5, 2001 ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fx0x7b%2Fobserving-behavioral-anomalies-in-web-applications-beyond-signature-scanners-g6p&title=Observing%20Behavioral%20Anomalies%20in%20Web%20Applications%20Beyond%20Signature%20Scanners&summary=Most%20web%20scanners%20rely%20on%20payload%20signatures%20and%20response%20matching.%20In%20practice%2C%20I%20often%20see%20cases...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:04 |
https://core.forem.com/new/performance | New Post - Forem Core Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Core Close Join the Forem Core Forem Core is a community of 3,676,891 amazing contributors 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 Forem Core? 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 Forem Core — Discussing the core forem open source software project — features, bugs, performance, self-hosting. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem Core © 2016 - 2026. Community building community Log in Create account | 2026-01-13T08:49:04 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fbogaboga1%2Fodoo-core-and-the-cost-of-reinventing-everything-15n1&title=Odoo%20Core%20and%20the%20Cost%20of%20Reinventing%20Everything&summary=Hello%2C%20this%20is%20my%20first%20blog%20post%20ever.%20I%E2%80%99d%20like%20to%20share%20my%20experience%20working%20with%20Odoo%2C%20an...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:04 |
https://docs.suprsend.com/docs/integrate-python-sdk | 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:49:04 |
https://docs.suprsend.com/docs/multi-lingual-template | Internationalization - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Templates Internationalization Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Templates Internationalization OpenAI Open in ChatGPT Guide on handling multiple languages in the template & publish language-specific versions. OpenAI Open in ChatGPT SuprSend allows you to create notifications in multiple languages in the same template. Once the languages are added, SuprSend will pick the preferred language from user’s profile and send the message as per the user’s language. You can set user preferred language using our Python or Node SDK English is the default fallback language. So users with no language preference set or preferred language for which content is not present in template will get the notification in English language. You can enable multi-lingual templates by simply following the below steps: 1 Add Languages In any template, English (en) language in enabled by default. To add other languages, click on Language button on the top right side of template editor. This will open language selection modal. Search the required language, add it and save the changes. 2 Add content for each language and Save Once the required languages are added, you’ll see the enabled languages in the side panel - draft version. The languages are set at template group level, that is it will be enabled for all the channels at once. However, you can choose which language content to publish at the time of publishing the draft. Add the content for each of these languages. 3 Publish Languages After making the changes, click on Publish draft button . Add a relevant version name and Click on Next . Select the languages that you want to Publish. English language will be published by default. If you see an error message below any language (Spanish in above image), that means there are some missing fields in the template form for that language. You’ll not be able to publish the language with incomplete information. You can go back, add the missing fields for that language and publish it again or skip this language and publish. That’s it. Published languages can now be seen in the live version. Was this page helpful? Yes No Suggest edits Raise issue Previous Users What does users stand for and how to manage user profiles in SuprSend Next ⌘ I x github linkedin youtube Powered by | 2026-01-13T08:49:04 |
https://dev.to/t/aws/page/6#main-content | Amazon Web Services Page 6 - 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 Amazon Web Services Follow Hide Amazon Web Services (AWS) is a collection of web services for computing, storage, machine learning, security, and more There are over 200+ AWS services as of 2023. Create Post submission guidelines Articles which primary focus is AWS are permitted to used the #aws tag. Older #aws posts 3 4 5 6 7 8 9 10 11 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How to Deploy Your Web App with AWS Elastic Beanstalk Samuel Ojo Samuel Ojo Samuel Ojo Follow Jan 7 How to Deploy Your Web App with AWS Elastic Beanstalk # webdev # aws # cloud # devops Comments Add Comment 6 min read Why I rescheduled my AWS exam today Ali-Funk Ali-Funk Ali-Funk Follow Jan 7 Why I rescheduled my AWS exam today # aws # beginners # cloud # career Comments Add Comment 2 min read Logging Into EC2 Is Easy… Until You Pick the Wrong Way Aishwary Gathe Aishwary Gathe Aishwary Gathe Follow Jan 9 Logging Into EC2 Is Easy… Until You Pick the Wrong Way # aws # cloud # security # ec2 1 reaction Comments 1 comment 3 min read Amazon Bedrock: From Zero to Production in 30 Minutes David Marcelo Petrocelli David Marcelo Petrocelli David Marcelo Petrocelli Follow Jan 7 Amazon Bedrock: From Zero to Production in 30 Minutes # aws # amazonbedrock # generativeai # python Comments Add Comment 4 min read 🌸 Nikte – Reconocimiento de flores con arquitectura serverless en AWS Fernando Gutierrez Fernando Gutierrez Fernando Gutierrez Follow Jan 7 🌸 Nikte – Reconocimiento de flores con arquitectura serverless en AWS # programming # ai # python # aws Comments Add Comment 3 min read 🚨 AWS 128: Setting Up Amazon ECR and Pushing Docker Images Hritik Raj Hritik Raj Hritik Raj Follow Jan 8 🚨 AWS 128: Setting Up Amazon ECR and Pushing Docker Images # aws # docker # ecr # 100daysofcloud Comments Add Comment 4 min read AWS Bedrock Security Best Practices: Building Secure Generative AI Applications Brayan Arrieta Brayan Arrieta Brayan Arrieta Follow Jan 7 AWS Bedrock Security Best Practices: Building Secure Generative AI Applications # machinelearning # ai # aws # security Comments Add Comment 4 min read Day 13: Sending AI Reports via Email using AWS SNS and Python. Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 8 Day 13: Sending AI Reports via Email using AWS SNS and Python. # aws # python # sns # devops Comments Add Comment 1 min read Automação de Backups para SFTP Externo Railander Marques Railander Marques Railander Marques Follow for AWS Community Builders Jan 7 Automação de Backups para SFTP Externo # sftp # lambda # automation # aws Comments Add Comment 13 min read Identify Services From Other In-Scope AWS Service Categories Ntombizakhona Mabaso Ntombizakhona Mabaso Ntombizakhona Mabaso Follow for AWS Community Builders Jan 7 Identify Services From Other In-Scope AWS Service Categories # aws # cloud # cloudcomputing # cloudpractitioner Comments Add Comment 5 min read 🚀 AWS 126: Instant Web Servers - Automating Nginx with User Data Hritik Raj Hritik Raj Hritik Raj Follow Jan 6 🚀 AWS 126: Instant Web Servers - Automating Nginx with User Data # aws # nginx # automation # 100daysofcloud Comments Add Comment 3 min read 🚀 My DevOps Journey: From Learning to Building on AWS with Containers Ravi Kumar Kushwaha Ravi Kumar Kushwaha Ravi Kumar Kushwaha Follow Jan 8 🚀 My DevOps Journey: From Learning to Building on AWS with Containers # kubernetes # devops # aws # docker Comments Add Comment 2 min read 7 Must-Have Amazon System Design Interview Resources to Nail Your Prep Dev Loops Dev Loops Dev Loops Follow Jan 6 7 Must-Have Amazon System Design Interview Resources to Nail Your Prep # aws # career # resources # systemdesign Comments Add Comment 4 min read EKS vs ECS: A Comprehensive Comparison Tandap Noel Bansikah Tandap Noel Bansikah Tandap Noel Bansikah Follow Jan 5 EKS vs ECS: A Comprehensive Comparison # aws # kubernetes # cloudnative # devops Comments Add Comment 5 min read Terraform State Management with Amazon S3 Tandap Noel Bansikah Tandap Noel Bansikah Tandap Noel Bansikah Follow Jan 7 Terraform State Management with Amazon S3 # terraform # infrastructureascode # aws # cloud Comments Add Comment 6 min read 🧱How to use Amazon Bedrock with Python (boto3) Fernando Gutierrez Fernando Gutierrez Fernando Gutierrez Follow Jan 7 🧱How to use Amazon Bedrock with Python (boto3) # ai # python # aws # programming Comments Add Comment 1 min read Experimenting with agentic player/coach workflows in Kiro CLI subagents Ricardo Sueiras Ricardo Sueiras Ricardo Sueiras Follow for AWS Jan 9 Experimenting with agentic player/coach workflows in Kiro CLI subagents # kiro # aws 5 reactions Comments Add Comment 7 min read Forwarding Cookies Using CloudFront: A Workaround for AWS Cache Policy Limitations Daniel Kraszewski Daniel Kraszewski Daniel Kraszewski Follow for u11d Jan 7 Forwarding Cookies Using CloudFront: A Workaround for AWS Cache Policy Limitations # devops # aws # cloudfront # terraform Comments Add Comment 4 min read Day 12: Building a simple RAG pipeline with Lambda, DynamoDB, and Bedrock. Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 7 Day 12: Building a simple RAG pipeline with Lambda, DynamoDB, and Bedrock. # aws # python # dynamodb # bedrock Comments Add Comment 1 min read Compare AWS Pricing Models Ntombizakhona Mabaso Ntombizakhona Mabaso Ntombizakhona Mabaso Follow for AWS Community Builders Jan 7 Compare AWS Pricing Models # aws # cloud # cloudcomputing # cloudpractitioner Comments Add Comment 4 min read Day 10: Storing Financial Data in DynamoDB with Python (Boto3). Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 6 Day 10: Storing Financial Data in DynamoDB with Python (Boto3). # dynamodb # aws # python # database Comments Add Comment 1 min read AWS DocumentDB Streams: Configuración y caso de uso olcortesb olcortesb olcortesb Follow for AWS Español Jan 7 AWS DocumentDB Streams: Configuración y caso de uso # aws # awddocumentdb # stream Comments Add Comment 6 min read How I Passed the AWS Certified Cloud Practitioner in 24 Days (For Free) Adedoyin Adedoyin Adedoyin Follow Jan 5 How I Passed the AWS Certified Cloud Practitioner in 24 Days (For Free) # aws # awscloudpractitioner # cloudcertification # examprep Comments Add Comment 3 min read AI-Augmented Cloud Operations Abhijeet Yadav Abhijeet Yadav Abhijeet Yadav Follow Jan 7 AI-Augmented Cloud Operations # aws # serverless # aiops # automation 1 reaction Comments Add Comment 6 min read Day 35: Deploying and Managing Applications on AWS Thu Kha Kyawe Thu Kha Kyawe Thu Kha Kyawe Follow Jan 7 Day 35: Deploying and Managing Applications on AWS # aws # 100daysofcloudaws Comments Add Comment 3 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/srikarsunchu/i-got-tired-of-waiting-for-gradle-so-i-built-a-runtime-that-runs-kotlin-like-python-10nl#what-is-elide | I got tired of waiting for Gradle, so I built a runtime that runs Kotlin like Python. - 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 Srikar Sunchu Posted on Jan 13 I got tired of waiting for Gradle, so I built a runtime that runs Kotlin like Python. # kotlin # performance # productivity # tooling I hit ./gradlew run and alt-tab to Discord. By the time I tab back, it's still resolving dependencies. This is a script. It's 40 lines. So I helped build something that doesn't make me wait. Elide . What is Elide? Elide is a runtime. Like Node. Like Python. You install it, you run code. curl -sSL elide.sh | bash Enter fullscreen mode Exit fullscreen mode But here's the thing: it doesn't just run one language. elide run app.kt # Kotlin, no Gradle elide run server.ts # TypeScript, no build step elide run script.py # Python, faster than CPython Enter fullscreen mode Exit fullscreen mode One binary. One toolchain. Multiple languages. Why this matters Most teams aren't single-language. You've got TypeScript on the frontend, Python for ML scripts, maybe Kotlin or Java somewhere in the backend. That's three runtimes, three package managers, three sets of problems. Elide is one runtime that speaks all of them. Install dependencies from npm and Maven in the same project. Run tests across languages with one command. No context switching. How it works Elide is built on GraalVM. The same compiler optimizes across languages-JavaScript, Python, Kotlin. No serialization when crossing language boundaries. All in one engine. What you can do today elide run — run code in any supported language elide test — run tests with built-in coverage elide install — fetch from npm or Maven elide serve — spin up a fast polyglot server Drop-in Gradle plugin for existing Java/Kotlin projects Try it Elide is in beta. curl -sSL elide.sh | bash Enter fullscreen mode Exit fullscreen mode We're on Discord if you want to talk, report bugs, or tell us what we're missing. Here's our Github - if you've read this far, leave us a star :) Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Baasil Ali Baasil Ali Baasil Ali Follow Joined Jan 13, 2026 • Jan 13 Dropdown menu Copy link Hide This is so sick! Like comment: Like comment: 2 likes Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Srikar Sunchu Follow Design engineer at Elide, where we're making Kotlin run like Python. I write about dev tools, terminal UIs, and why your build is too slow. Location San Francisco Work Design Engineer @ Elide Joined Jan 12, 2026 Trending on DEV Community Hot From CDN to Pixel: A React App's Journey # react # programming # webdev # performance What was your win this week??? # weeklyretro # discuss How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://tools.google.com/dlpage/gaoptout | Google 애널리틱스 차단 브라우저 부가 기능 다운로드 페이지 크롬 다운로드에는 자바스크립트가 지원되는 브라우저가 필요합니다. 브라우저에서 자바스크립트를 사용하도록 설정하는 방법은 여기에서 알아보세요. Select a language ‫العربية‬ ‪Deutsch‬ ‪English‬ ‪English (UK)‬ ‪español‬ ‪français‬ ‪italiano‬ ‪日本語‬ ‪한국어‬ ‪Nederlands‬ ‪polski‬ ‪português (Brasil)‬ ‪русский‬ ‪ไทย‬ ‪Türkçe‬ ‪简体中文‬ ‪繁體中文 (台灣)‬ Google 애널리틱스 차단 브라우저 부가 기능 웹사이트 방문자가 자신의 데이터를 Google 애널리틱스에서 사용하지 못하도록 설정하는 기능을 제공하기 위해, Google에서는 지원되는 버전의 Google 애널리틱스 자바스크립트(analytics.js, gtag.js)를 사용하는 웹사이트를 대상으로 Google 애널리틱스 분석 차단 브라우저 부가 기능을 개발했습니다. 개인 데이터 사용을 차단하려면 사용 중인 웹브라우저에 맞는 부가 기능을 다운로드하여 설치하세요. Google 애널리틱스 분석 차단 부가 기능은 Chrome, Safari, Firefox, Microsoft Edge와 호환되도록 설계되었습니다. 차단 부가 기능이 작동하려면 브라우저에서 올바르게 로드되고 실행될 수 있어야 합니다. 개인 데이터 사용 차단 및 브라우저 부가 기능을 올바르게 설치하는 방법은 여기 에서 자세히 알아보세요. 귀하의 브라우저에서는 Google 애널리틱스 차단 브라우저 부가 기능이 지원되지 않습니다. Chrome, Mozilla Firefox, Apple Safari, Microsoft Edge를 지원합니다. Google 애널리틱스 개인정보 보호에 대해 자세히 알아보십시오. » ©2026 Google - 개인정보 보호정책 - 도움말 | 2026-01-13T08:49:04 |
https://pypy.org/ | PyPy Skip to main content Features What is PyPy? Compatibility Performance Download Dev Docs Blog Index Tags Archive by year RSS feed Old site About Bluesky IRC logs YouTube Twitch Sponsors How To Help? Contact PyPy A fast , compliant alternative implementation of Python Download PyPy What is PyPy ? Documentation (external link) On average, PyPy is about 3 times faster than CPython 3.11. We currently support python 3.11 and 2.7. PyPy (with JIT) benchmark times normalized to CPython. Smaller is better. Based on the geometric average of all benchmarks "... we are avid fans of PyPy and commensurately thankful for the great work by the PyPy team over the years. PyPy has enabled us to use Python for a larger part of our toolset than CPython alone would have supported, and its smooth integration with C/C++ through CFFI has helped us attain a better tradeoff between performance and programmer productivity in our projects" -- Vilhjálmur Þorsteinsson, founder and CEO of Miðeind, Feb 2022 Advantages and distinct Features Speed: thanks to its Just-in-Time compiler, Python programs often run faster on PyPy. (What is a JIT compiler?) Memory usage: memory-hungry Python programs (several hundreds of MBs or more) might end up taking less space than they do in CPython. Compatibility: PyPy is highly compatible with existing python code. It supports cffi , cppyy , and can run popular python libraries like twisted , and django . It can also run NumPy, Scikit-learn and more via a c-extension compatibility layer. Stackless: PyPy comes by default with support for stackless mode , providing micro-threads for massive concurrency. As well as other features . © 2025 The PyPy Team Built with Nikola Last built 2025-10-13T14:18 RSS feed | 2026-01-13T08:49:04 |
https://zeroday.forem.com/t/iam | Iam - Security Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Security Forem Close # iam Follow Hide Identity and Access Management principles, technologies, and best practices. Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Passwordless Isn't the Future It's Already Here (And IAM Is Being Rewritten) Sunny Sinha Sunny Sinha Sunny Sinha Follow Jan 9 Passwordless Isn't the Future It's Already Here (And IAM Is Being Rewritten) # iam # saas # password # cybersecurity Comments Add Comment 3 min read The IAM Blind Spot Everyone Is Ignoring: Non-Human Identities Are Taking Over Sunny Sinha Sunny Sinha Sunny Sinha Follow Jan 5 The IAM Blind Spot Everyone Is Ignoring: Non-Human Identities Are Taking Over # identity # cybersecurity # saas # iam Comments Add Comment 3 min read 🔍 November: Strengthening Identity & Access Management (IAM) for SMBs Amit Ambekar Amit Ambekar Amit Ambekar Follow Nov 28 '25 🔍 November: Strengthening Identity & Access Management (IAM) for SMBs # iam # cybersecurity # soc # education Comments Add Comment 2 min read Why the Directory Is the Core of IAM: The Digital Heartbeat of Every Organization Sunny Sinha Sunny Sinha Sunny Sinha Follow Nov 27 '25 Why the Directory Is the Core of IAM: The Digital Heartbeat of Every Organization # identity # security # iam # activedirectory Comments Add Comment 3 min read The Rise of ITDR: Why Identity Threat Detection & Response Is Becoming the New Frontline of Cybersecurity Sunny Sinha Sunny Sinha Sunny Sinha Follow Dec 12 '25 The Rise of ITDR: Why Identity Threat Detection & Response Is Becoming the New Frontline of Cybersecurity # identity # cybersecurity # iam # saas 1 reaction Comments Add Comment 3 min read loading... trending guides/resources The IAM Blind Spot Everyone Is Ignoring: Non-Human Identities Are Taking Over Passwordless Isn't the Future It's Already Here (And IAM Is Being Rewritten) The Rise of ITDR: Why Identity Threat Detection & Response Is Becoming the New Frontline of Cyber... Why the Directory Is the Core of IAM: The Digital Heartbeat of Every Organization 🔍 November: Strengthening Identity & Access Management (IAM) for SMBs 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/ojosamuel129/how-to-deploy-your-web-app-with-aws-elastic-beanstalk-35n1#comments | How to Deploy Your Web App with AWS Elastic Beanstalk - 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 Samuel Ojo Posted on Jan 7 How to Deploy Your Web App with AWS Elastic Beanstalk # webdev # aws # devops # cloud AWS Elastic Beanstalk is a Platform-as-a-Service (PaaS) that simplifies application deployment and management. It automatically handles capacity provisioning, allowing developers to focus on writing code rather than managing infrastructure. You simply provide your code while Beanstalk handles: EC2 instances Load Balancing & Auto Scaling Application health checks Logs & Metrics Rolling updates and blue/green deployments Supported platforms include: Java, .NET, Node.js, Python, PHP, Ruby, Go, Docker. Key benefits: Scalability Automation Integration with AWS services Step 1: Sign in to the AWS Management Console Go to the AWS Management Console and sign in with your AWS account. Navigate to Elastic Beanstalk In the AWS search bar, type Elastic Beanstalk Select Elastic Beanstalk from the services list Step 2: Create a New Application Click Create application Enter an Application name (for example: getting-started-app) (Optional) Add a description Step 3: Choose Your Platform Under Platform , select the programming language your app uses Examples: Node.js, Java, Python, PHP, .NET, Ruby, etc. For me, its Node.js . Choose the platform version (you can leave the default) Step 4: Upload Your Application Code Under Application code , choose: Sample application (recommended for first-time users), or Upload your code (if you already have an app) If uploading your code, select your file (ZIP format) Step 5: Configure Application Settings (Service Role, Instance Profile, and Key Pair) Configure security and access settings so Elastic Beanstalk can manage AWS resources so you can securely access your EC2 instances. 5.1: Configure the Elastic Beanstalk Service Role The service role allows Elastic Beanstalk to interact with other AWS services on your behalf. Configure service access Next, you need two roles: Service role EC2 instance profile role A service role allows Elastic Beanstalk to monitor your EC2 instances and upgrade your environment’s platform. An EC2 instance profile role permits tasks such as writing logs and interacting with other services. Create Service role If you have previously created a Service role and would like to choose an existing one, select the value from the Service role drop-down. If not, proceed to create a new one. For Service role , choose Create role . For Trusted entity type , choose AWS service and leave the rest as default. Verify that Permissions policies include the following, then choose Next : Click Create role . Return to the Configure service access tab, refresh the list, then select the newly created service role . 5.2 Create EC2 instance profile The E* C2 instance profile * allows EC2 instances in your environment to access AWS services securely. You can choose an existing one from the EC2 instance profile drop-down or create a new one. Select Create role . For Trusted entity type , choose AWS service and leave the rest as default and click Next . Verify that Permissions policies include the following, then click Next . Select Create role . Return to the Configure service access tab, refresh the list, then select the newly created EC2 instance profile . Now you need to configure and create your application 5.3: Select a Key Pair A key pair allows you to securely connect to the EC2 instances created by Elastic Beanstalk . Under EC2 key pair : Select an existing key pair , or Click Create a new key pair . I do have an existing key pair , but i will create a new one for the sake of this tutorial. To create key pair , open your AWS console in another tab, type key pairs in the search bar and select key pairs . Enter a key pair name Ensure you Download and store the key file securely Without a key pair , you will not be able to connect to the EC2 instance using SSH . Optional steps: networking, databases, scaling parameters, advanced configuration for updates, monitoring, and logging. On the Review page, which shows a summary of your choices, select Submit . 5.4: Review Other Settings (Optional) You can either keep the default settings or adjust them if needed: - Instance type (EC2 size) - Auto scaling options - Environment variables - Security groups Click Create . Step 6: Creating the Environment for the application AWS will automatically set up the required resources, including: EC2 instances Auto Scaling group Load balancer Monitoring and health checks Please note that This process may take a few minutes. Once completed, your application will be live. Evidence of Beanstalk being LIVE To access the EC2 created On the AWS Console , search for EC2 Check the dashboard to confirm the instance status is running Select the App created and then connect . The EC2 instance created while setting up the Elastic Beanstalk is shown below: S3 Bucket created Auto Scaling group created Step 7: Cleaning up your Elastic Beanstalk environment and Terminate the Application Terminate the environment when you’re done in order to stop billing. To delete the application and all associated resources, ensure you delete all application versions. Open the Elastic Beanstalk console, and in the Regions list , select your AWS Region . In the navigation pane , choose Applications , and then choose your app (the name you gave your app) and choose Application versions . On the Application versions page, select all application versions that you want to delete. Choose Actions , and then choose Delete . Turn on Delete versions from Amazon S3. Choose Delete , and then choose Done . Conclusion AWS Elastic Beanstalk is an excellent choice for developers who want to deploy applications quickly without managing servers manually. It provides a balance between control and automation, making it ideal for small projects and enterprise applications alike. By leveraging Elastic Beanstalk , you can focus on building great software while AWS handles the heavy lifting of infrastructure management. Ensure you continue building, learning and developing as many applications as possible :). Thanks for reading, see you in the next one. 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 Samuel Ojo Follow Passionate about technology with a strong focus on empowering businesses through modern workplace solutions, cloud-native architectures, and DevOps practices. Joined Oct 19, 2025 More from Samuel Ojo Deploy and configure Azure Monitor # azure # cloud # architecture How to Launch an EC2 Instance in AWS # webdev # aws # ec2 # cloud How to Add a Data Disk to a VM # azure # cloud # virtualmachine # cloudstorage 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://docs.python.org/3/license.html#execution-tracing | 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:49:04 |
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:49:04 |
https://peps.python.org#introduction | PEP 0 – Index of Python Enhancement Proposals (PEPs) | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 0 Toggle light / dark / auto colour theme PEP 0 – Index of Python Enhancement Proposals (PEPs) Author : The PEP Editors Status : Active Type : Informational Created : 13-Jul-2000 Table of Contents Introduction Topics API Numerical Index Index by Category Process and Meta-PEPs Other Informational PEPs Provisional PEPs (provisionally accepted; interface may still change) Accepted PEPs (accepted; may not be implemented yet) Open PEPs (under consideration) Finished PEPs (done, with a stable interface) Historical Meta-PEPs and Informational PEPs Deferred PEPs (postponed pending further research or updates) Rejected, Superseded, and Withdrawn PEPs Reserved PEP Numbers PEP Types Key PEP Status Key Authors/Owners Introduction This PEP contains the index of all Python Enhancement Proposals, known as PEPs. PEP numbers are assigned by the PEP editors, and once assigned are never changed. The version control history of the PEP texts represent their historical record. Topics PEPs for specialist subjects are indexed by topic . Governance PEPs Packaging PEPs Release PEPs Typing PEPs API The PEPS API is a JSON file of metadata about all the published PEPs. Read more here . Numerical Index The numerical index contains a table of all PEPs, ordered by number. Index by Category Process and Meta-PEPs PEP Title Authors PA 1 PEP Purpose and Guidelines Barry Warsaw, Jeremy Hylton, David Goodger, Alyssa Coghlan PA 2 Procedure for Adding New Modules Brett Cannon, Martijn Faassen PA 4 Deprecation of Standard Modules Brett Cannon, Martin von Löwis PA 7 Style Guide for C Code Guido van Rossum, Barry Warsaw PA 8 Style Guide for Python Code Guido van Rossum, Barry Warsaw, Alyssa Coghlan PA 10 Voting Guidelines Barry Warsaw PA 11 CPython platform support Martin von Löwis, Brett Cannon PA 12 Sample reStructuredText PEP Template David Goodger, Barry Warsaw, Brett Cannon PA 13 Python Language Governance The Python core team and community PA 387 Backwards Compatibility Policy Benjamin Peterson PA 545 Python Documentation Translations Julien Palard, Inada Naoki, Victor Stinner PA 602 Annual Release Cycle for Python Łukasz Langa 3.9 PA 609 Python Packaging Authority (PyPA) Governance Dustin Ingram, Pradyun Gedam, Sumana Harihareswara PA 676 PEP Infrastructure Process Adam Turner PA 729 Typing governance process Jelle Zijlstra, Shantanu Jain PA 731 C API Working Group Charter Guido van Rossum, Petr Viktorin, Victor Stinner, Steve Dower, Irit Katriel PA 732 The Python Documentation Editorial Board Joanna Jablonski PA 761 Deprecating PGP signatures for CPython artifacts Seth Michael Larson 3.14 PA 811 Defining Python Security Response Team membership and responsibilities Seth Michael Larson Other Informational PEPs PEP Title Authors IA 20 The Zen of Python Tim Peters IA 101 Doing Python Releases 101 Barry Warsaw, Guido van Rossum IF 247 API for Cryptographic Hash Functions A.M. Kuchling IF 248 Python Database API Specification v1.0 Greg Stein, Marc-André Lemburg IF 249 Python Database API Specification v2.0 Marc-André Lemburg IA 257 Docstring Conventions David Goodger, Guido van Rossum IF 272 API for Block Encryption Algorithms v1.0 A.M. Kuchling IA 287 reStructuredText Docstring Format David Goodger IA 290 Code Migration and Modernization Raymond Hettinger IF 333 Python Web Server Gateway Interface v1.0 Phillip J. Eby IA 394 The “python” Command on Unix-Like Systems Kerrick Staley, Alyssa Coghlan, Barry Warsaw, Petr Viktorin, Miro Hrončok, Carol Willing IF 399 Pure Python/C Accelerator Module Compatibility Requirements Brett Cannon 3.3 IF 430 Migrating to Python 3 as the default online documentation Alyssa Coghlan IA 434 IDLE Enhancement Exception for All Branches Todd Rovito, Terry Reedy IF 452 API for Cryptographic Hash Functions v2.0 A.M. Kuchling, Christian Heimes IF 457 Notation For Positional-Only Parameters Larry Hastings IF 482 Literature Overview for Type Hints Łukasz Langa IF 483 The Theory of Type Hints Guido van Rossum, Ivan Levkivskyi IA 514 Python registration in the Windows registry Steve Dower IF 579 Refactoring C functions and methods Jeroen Demeyer IF 588 GitHub Issues Migration Plan Mariatta IF 607 Reducing CPython’s Feature Delivery Latency Łukasz Langa, Steve Dower, Alyssa Coghlan 3.9 IA 619 Python 3.10 Release Schedule Pablo Galindo Salgado 3.10 IF 630 Isolating Extension Modules Petr Viktorin IF 635 Structural Pattern Matching: Motivation and Rationale Tobias Kohn, Guido van Rossum 3.10 IF 636 Structural Pattern Matching: Tutorial Daniel F Moisset 3.10 IF 659 Specializing Adaptive Interpreter Mark Shannon IA 664 Python 3.11 Release Schedule Pablo Galindo Salgado 3.11 IA 672 Unicode-related Security Considerations for Python Petr Viktorin IA 693 Python 3.12 Release Schedule Thomas Wouters 3.12 IA 719 Python 3.13 Release Schedule Thomas Wouters 3.13 IF 733 An Evaluation of Python’s Public C API Erlend Egeberg Aasland, Domenico Andreoli, Stefan Behnel, Carl Friedrich Bolz-Tereick, Simon Cross, Steve Dower, Tim Felgentreff, David Hewitt, Shantanu Jain, Wenzel Jakob, Irit Katriel, Marc-Andre Lemburg, Donghee Na, Karl Nelson, Ronald Oussoren, Antoine Pitrou, Neil Schemenauer, Mark Shannon, Stepan Sindelar, Gregory P. Smith, Eric Snow, Victor Stinner, Guido van Rossum, Petr Viktorin, Carol Willing, William Woodruff, David Woods, Jelle Zijlstra IA 745 Python 3.14 Release Schedule Hugo van Kemenade 3.14 IF 762 REPL-acing the default REPL Pablo Galindo Salgado, Łukasz Langa, Lysandros Nikolaou, Emily Morehouse-Valcarcel 3.13 IA 790 Python 3.15 Release Schedule Hugo van Kemenade 3.15 IA 801 Reserved Barry Warsaw IF 3333 Python Web Server Gateway Interface v1.0.1 Phillip J. Eby IF 8000 Python Language Governance Proposal Overview Barry Warsaw IF 8002 Open Source Governance Survey Barry Warsaw, Łukasz Langa, Antoine Pitrou, Doug Hellmann, Carol Willing IA 8016 The Steering Council Model Nathaniel J. Smith, Donald Stufft IF 8100 January 2019 Steering Council election Nathaniel J. Smith, Ee Durbin IF 8101 2020 Term Steering Council election Ewa Jodlowska, Ee Durbin IF 8102 2021 Term Steering Council election Ewa Jodlowska, Ee Durbin, Joe Carey IF 8103 2022 Term Steering Council election Ewa Jodlowska, Ee Durbin, Joe Carey IF 8104 2023 Term Steering Council election Ee Durbin IF 8105 2024 Term Steering Council election Ee Durbin IF 8106 2025 Term Steering Council election Ee Durbin IF 8107 2026 Term Steering Council election Ee Durbin Provisional PEPs (provisionally accepted; interface may still change) PEP Title Authors SP 708 Extending the Repository API to Mitigate Dependency Confusion Attacks Donald Stufft Accepted PEPs (accepted; may not be implemented yet) PEP Title Authors SA 458 Secure PyPI downloads with signed repository metadata Trishank Karthik Kuppusamy, Vladimir Diaz, Marina Moore, Lukas Puehringer, Joshua Lock, Lois Anne DeLong, Justin Cappos SA 658 Serve Distribution Metadata in the Simple Repository API Tzu-ping Chung SA 668 Marking Python base environments as “externally managed” Geoffrey Thomas, Matthias Klose, Filipe Laíns, Donald Stufft, Tzu-ping Chung, Stefano Rivera, Elana Hashman, Pradyun Gedam SA 686 Make UTF-8 mode default Inada Naoki 3.15 SA 687 Isolating modules in the standard library Erlend Egeberg Aasland, Petr Viktorin 3.12 SA 691 JSON-based Simple API for Python Package Indexes Donald Stufft, Pradyun Gedam, Cooper Lees, Dustin Ingram SA 699 Remove private dict version field added in PEP 509 Ken Jin 3.12 SA 701 Syntactic formalization of f-strings Pablo Galindo Salgado, Batuhan Taskaya, Lysandros Nikolaou, Marta Gómez Macías 3.12 SA 703 Making the Global Interpreter Lock Optional in CPython Sam Gross 3.13 SA 714 Rename dist-info-metadata in the Simple API Donald Stufft SA 728 TypedDict with Typed Extra Items Zixuan James Li 3.15 SA 739 build-details.json 1.0 — a static description file for Python build details Filipe Laíns 3.14 SA 753 Uniform project URLs in core metadata William Woodruff, Facundo Tuesca SA 770 Improving measurability of Python packages with Software Bill-of-Materials Seth Larson SA 773 A Python Installation Manager for Windows Steve Dower SA 793 PyModExport: A new entry point for C extension modules Petr Viktorin 3.15 SA 794 Import Name Metadata Brett Cannon SA 798 Unpacking in Comprehensions Adam Hartz, Erik Demaine 3.15 SA 799 A dedicated profiling package for organizing Python profiling tools Pablo Galindo Salgado, László Kiss Kollár 3.15 SA 810 Explicit lazy imports Pablo Galindo Salgado, Germán Méndez Bravo, Thomas Wouters, Dino Viehland, Brittany Reynoso, Noah Kim, Tim Stumbaugh 3.15 Open PEPs (under consideration) PEP Title Authors S 467 Minor API improvements for binary sequences Alyssa Coghlan, Ethan Furman 3.15 S 480 Surviving a Compromise of PyPI: End-to-end signing of packages Trishank Karthik Kuppusamy, Vladimir Diaz, Justin Cappos, Marina Moore S 603 Adding a frozenmap type to collections Yury Selivanov S 638 Syntactic Macros Mark Shannon S 653 Precise Semantics for Pattern Matching Mark Shannon S 671 Syntax for late-bound function argument defaults Chris Angelico 3.12 S 694 Upload 2.0 API for Python Package Indexes Barry Warsaw, Donald Stufft, Ee Durbin S 710 Recording the provenance of installed packages Fridolín Pokorný S 711 PyBI: a standard format for distributing Python Binaries Nathaniel J. Smith S 718 Subscriptable functions James Hilton-Balfe 3.15 I 720 Cross-compiling Python packages Filipe Laíns 3.12 S 725 Specifying external dependencies in pyproject.toml Pradyun Gedam, Jaime Rodríguez-Guerra, Ralf Gommers S 743 Add Py_OMIT_LEGACY_API to the Python C API Victor Stinner, Petr Viktorin 3.15 I 744 JIT Compilation Brandt Bucher, Savannah Ostrowski 3.13 S 746 Type checking Annotated metadata Adrian Garcia Badaracco 3.15 S 747 Annotating Type Forms David Foster, Eric Traut 3.15 S 748 A Unified TLS API for Python Joop van de Pol, William Woodruff 3.14 S 752 Implicit namespaces for package repositories Ofek Lev, Jarek Potiuk P 755 Implicit namespace policy for PyPI Ofek Lev S 764 Inline typed dictionaries Victorien Plot 3.15 I 766 Explicit Priority Choices Among Multiple Indexes Michael Sarahan S 767 Annotating Read-Only Attributes Eneg 3.15 S 771 Default Extras for Python Software Packages Thomas Robitaille, Jonathan Dekhtiar P 772 Packaging Council governance process Barry Warsaw, Deb Nicholson, Pradyun Gedam I 776 Emscripten Support Hood Chatham 3.14 S 777 How to Re-invent the Wheel Emma Harper Smith S 780 ABI features as environment markers Klaus Zimmermann, Ralf Gommers 3.14 S 781 Make TYPE_CHECKING a built-in constant Inada Naoki 3.15 S 783 Emscripten Packaging Hood Chatham S 785 New methods for easier handling of ExceptionGroups Zac Hatfield-Dodds 3.14 S 788 Protecting the C API from Interpreter Finalization Peter Bierma 3.15 S 789 Preventing task-cancellation bugs by limiting yield in async generators Zac Hatfield-Dodds, Nathaniel J. Smith 3.14 S 800 Disjoint bases in the type system Jelle Zijlstra 3.15 S 802 Display Syntax for the Empty Set Adam Turner 3.15 S 803 Stable ABI for Free-Threaded Builds Petr Viktorin 3.15 S 804 An external dependency registry and name mapping mechanism Pradyun Gedam, Ralf Gommers, Michał Górny, Jaime Rodríguez-Guerra, Michael Sarahan S 806 Mixed sync/async context managers with precise async marking Zac Hatfield-Dodds 3.15 S 807 Index support for Trusted Publishing William Woodruff S 808 Including static values in dynamic project metadata Henry Schreiner, Cristian Le S 809 Stable ABI for the Future Steve Dower 3.15 S 814 Add frozendict built-in type Victor Stinner, Donghee Na 3.15 S 815 Deprecate RECORD.jws and RECORD.p7s Konstantin Schütze, William Woodruff I 816 WASI Support Brett Cannon S 819 JSON Package Metadata Emma Harper Smith S 820 PySlot: Unified slot system for the C API Petr Viktorin 3.15 S 822 Dedented Multiline String (d-string) Inada Naoki 3.15 Finished PEPs (done, with a stable interface) PEP Title Authors SF 100 Python Unicode Integration Marc-André Lemburg 2.0 SF 201 Lockstep Iteration Barry Warsaw 2.0 SF 202 List Comprehensions Barry Warsaw 2.0 SF 203 Augmented Assignments Thomas Wouters 2.0 SF 205 Weak References Fred L. Drake, Jr. 2.1 SF 207 Rich Comparisons Guido van Rossum, David Ascher 2.1 SF 208 Reworking the Coercion Model Neil Schemenauer, Marc-André Lemburg 2.1 SF 214 Extended Print Statement Barry Warsaw 2.0 SF 217 Display Hook for Interactive Use Moshe Zadka 2.1 SF 218 Adding a Built-In Set Object Type Greg Wilson, Raymond Hettinger 2.2 SF 221 Import As Thomas Wouters 2.0 SF 223 Change the Meaning of x Escapes Tim Peters 2.0 SF 227 Statically Nested Scopes Jeremy Hylton 2.1 SF 229 Using Distutils to Build Python A.M. Kuchling 2.1 SF 230 Warning Framework Guido van Rossum 2.1 SF 232 Function Attributes Barry Warsaw 2.1 SF 234 Iterators Ka-Ping Yee, Guido van Rossum 2.1 SF 235 Import on Case-Insensitive Platforms Tim Peters 2.1 SF 236 Back to the __future__ Tim Peters 2.1 SF 237 Unifying Long Integers and Integers Moshe Zadka, Guido van Rossum 2.2 SF 238 Changing the Division Operator Moshe Zadka, Guido van Rossum 2.2 SF 250 Using site-packages on Windows Paul Moore 2.2 SF 252 Making Types Look More Like Classes Guido van Rossum 2.2 SF 253 Subtyping Built-in Types Guido van Rossum 2.2 SF 255 Simple Generators Neil Schemenauer, Tim Peters, Magnus Lie Hetland 2.2 SF 260 Simplify xrange() Guido van Rossum 2.2 SF 261 Support for “wide” Unicode characters Paul Prescod 2.2 SF 263 Defining Python Source Code Encodings Marc-André Lemburg, Martin von Löwis 2.3 SF 264 Future statements in simulated shells Michael Hudson 2.2 SF 273 Import Modules from Zip Archives James C. Ahlstrom 2.3 SF 274 Dict Comprehensions Barry Warsaw 2.7, 3.0 SF 277 Unicode file name support for Windows NT Neil Hodgson 2.3 SF 278 Universal Newline Support Jack Jansen 2.3 SF 279 The enumerate() built-in function Raymond Hettinger 2.3 SF 282 A Logging System Vinay Sajip, Trent Mick 2.3 SF 285 Adding a bool type Guido van Rossum 2.3 SF 289 Generator Expressions Raymond Hettinger 2.4 SF 292 Simpler String Substitutions Barry Warsaw 2.4 SF 293 Codec Error Handling Callbacks Walter Dörwald 2.3 SF 301 Package Index and Metadata for Distutils Richard Jones 2.3 SF 302 New Import Hooks Just van Rossum, Paul Moore 2.3 SF 305 CSV File API Kevin Altis, Dave Cole, Andrew McNamara, Skip Montanaro, Cliff Wells 2.3 SF 307 Extensions to the pickle protocol Guido van Rossum, Tim Peters 2.3 SF 308 Conditional Expressions Guido van Rossum, Raymond Hettinger 2.5 SF 309 Partial Function Application Peter Harris 2.5 SF 311 Simplified Global Interpreter Lock Acquisition for Extensions Mark Hammond 2.3 SF 318 Decorators for Functions and Methods Kevin D. Smith, Jim J. Jewett, Skip Montanaro, Anthony Baxter 2.4 SF 322 Reverse Iteration Raymond Hettinger 2.4 SF 324 subprocess - New process module Peter Astrand 2.4 SF 327 Decimal Data Type Facundo Batista 2.4 SF 328 Imports: Multi-Line and Absolute/Relative Aahz 2.4, 2.5, 2.6 SF 331 Locale-Independent Float/String Conversions Christian R. Reis 2.4 SF 338 Executing modules as scripts Alyssa Coghlan 2.5 SF 341 Unifying try-except and try-finally Georg Brandl 2.5 SF 342 Coroutines via Enhanced Generators Guido van Rossum, Phillip J. Eby 2.5 SF 343 The “with” Statement Guido van Rossum, Alyssa Coghlan 2.5 SF 352 Required Superclass for Exceptions Brett Cannon, Guido van Rossum 2.5 SF 353 Using ssize_t as the index type Martin von Löwis 2.5 SF 357 Allowing Any Object to be Used for Slicing Travis Oliphant 2.5 SF 358 The “bytes” Object Neil Schemenauer, Guido van Rossum 2.6, 3.0 SF 362 Function Signature Object Brett Cannon, Jiwon Seo, Yury Selivanov, Larry Hastings 3.3 SF 366 Main module explicit relative imports Alyssa Coghlan 2.6, 3.0 SF 370 Per user site-packages directory Christian Heimes 2.6, 3.0 SF 371 Addition of the multiprocessing package to the standard library Jesse Noller, Richard Oudkerk 2.6, 3.0 SF 372 Adding an ordered dictionary to collections Armin Ronacher, Raymond Hettinger 2.7, 3.1 SF 376 Database of Installed Python Distributions Tarek Ziadé 2.7, 3.2 SF 378 Format Specifier for Thousands Separator Raymond Hettinger 2.7, 3.1 SF 380 Syntax for Delegating to a Subgenerator Gregory Ewing 3.3 SF 383 Non-decodable Bytes in System Character Interfaces Martin von Löwis 3.1 SF 384 Defining a Stable ABI Martin von Löwis 3.2 SF 389 argparse - New Command Line Parsing Module Steven Bethard 2.7, 3.2 SF 391 Dictionary-Based Configuration For Logging Vinay Sajip 2.7, 3.2 SF 393 Flexible String Representation Martin von Löwis 3.3 SF 397 Python launcher for Windows Mark Hammond, Martin von Löwis 3.3 SF 405 Python Virtual Environments Carl Meyer 3.3 SF 409 Suppressing exception context Ethan Furman 3.3 SF 412 Key-Sharing Dictionary Mark Shannon 3.3 SF 414 Explicit Unicode Literal for Python 3.3 Armin Ronacher, Alyssa Coghlan 3.3 SF 415 Implement context suppression with exception attributes Benjamin Peterson 3.3 SF 417 Including mock in the Standard Library Michael Foord 3.3 SF 418 Add monotonic time, performance counter, and process time functions Cameron Simpson, Jim J. Jewett, Stephen J. Turnbull, Victor Stinner 3.3 SF 420 Implicit Namespace Packages Eric V. Smith 3.3 SF 421 Adding sys.implementation Eric Snow 3.3 SF 424 A method for exposing a length hint Alex Gaynor 3.4 SF 425 Compatibility Tags for Built Distributions Daniel Holth 3.4 SF 427 The Wheel Binary Package Format 1.0 Daniel Holth SF 428 The pathlib module – object-oriented filesystem paths Antoine Pitrou 3.4 SF 435 Adding an Enum type to the Python standard library Barry Warsaw, Eli Bendersky, Ethan Furman 3.4 SF 436 The Argument Clinic DSL Larry Hastings 3.4 SF 440 Version Identification and Dependency Specification Alyssa Coghlan, Donald Stufft SF 441 Improving Python ZIP Application Support Daniel Holth, Paul Moore 3.5 SF 442 Safe object finalization Antoine Pitrou 3.4 SF 443 Single-dispatch generic functions Łukasz Langa 3.4 SF 445 Add new APIs to customize Python memory allocators Victor Stinner 3.4 SF 446 Make newly created file descriptors non-inheritable Victor Stinner 3.4 SF 448 Additional Unpacking Generalizations Joshua Landau 3.5 SF 450 Adding A Statistics Module To The Standard Library Steven D’Aprano 3.4 SF 451 A ModuleSpec Type for the Import System Eric Snow 3.4 SF 453 Explicit bootstrapping of pip in Python installations Donald Stufft, Alyssa Coghlan SF 454 Add a new tracemalloc module to trace Python memory allocations Victor Stinner 3.4 SF 456 Secure and interchangeable hash algorithm Christian Heimes 3.4 SF 461 Adding % formatting to bytes and bytearray Ethan Furman 3.5 SF 465 A dedicated infix operator for matrix multiplication Nathaniel J. Smith 3.5 SF 466 Network Security Enhancements for Python 2.7.x Alyssa Coghlan 2.7.9 SF 468 Preserving the order of **kwargs in a function. Eric Snow 3.6 SF 471 os.scandir() function – a better and faster directory iterator Ben Hoyt 3.5 SF 475 Retry system calls failing with EINTR Charles-François Natali, Victor Stinner 3.5 SF 476 Enabling certificate verification by default for stdlib http clients Alex Gaynor 2.7.9, 3.4.3, 3.5 SF 477 Backport ensurepip (PEP 453) to Python 2.7 Donald Stufft, Alyssa Coghlan SF 479 Change StopIteration handling inside generators Chris Angelico, Guido van Rossum 3.5 SF 484 Type Hints Guido van Rossum, Jukka Lehtosalo, Łukasz Langa 3.5 SF 485 A Function for testing approximate equality Christopher Barker 3.5 SF 486 Make the Python Launcher aware of virtual environments Paul Moore 3.5 SF 487 Simpler customisation of class creation Martin Teichmann 3.6 SF 488 Elimination of PYO files Brett Cannon 3.5 SF 489 Multi-phase extension module initialization Petr Viktorin, Stefan Behnel, Alyssa Coghlan 3.5 SF 492 Coroutines with async and await syntax Yury Selivanov 3.5 SF 493 HTTPS verification migration tools for Python 2.7 Alyssa Coghlan, Robert Kuska, Marc-André Lemburg 2.7.12 SF 495 Local Time Disambiguation Alexander Belopolsky, Tim Peters 3.6 SF 498 Literal String Interpolation Eric V. Smith 3.6 SF 503 Simple Repository API Donald Stufft SF 506 Adding A Secrets Module To The Standard Library Steven D’Aprano 3.6 SF 508 Dependency specification for Python Software Packages Robert Collins SF 515 Underscores in Numeric Literals Georg Brandl, Serhiy Storchaka 3.6 SF 517 A build-system independent format for source trees Nathaniel J. Smith, Thomas Kluyver SF 518 Specifying Minimum Build System Requirements for Python Projects Brett Cannon, Nathaniel J. Smith, Donald Stufft SF 519 Adding a file system path protocol Brett Cannon, Koos Zevenhoven 3.6 SF 520 Preserving Class Attribute Definition Order Eric Snow 3.6 SF 523 Adding a frame evaluation API to CPython Brett Cannon, Dino Viehland 3.6 SF 524 Make os.urandom() blocking on Linux Victor Stinner 3.6 SF 525 Asynchronous Generators Yury Selivanov 3.6 SF 526 Syntax for Variable Annotations Ryan Gonzalez, Philip House, Ivan Levkivskyi, Lisa Roach, Guido van Rossum 3.6 SF 527 Removing Un(der)used file types/extensions on PyPI Donald Stufft SF 528 Change Windows console encoding to UTF-8 Steve Dower 3.6 SF 529 Change Windows filesystem encoding to UTF-8 Steve Dower 3.6 SF 530 Asynchronous Comprehensions Yury Selivanov 3.6 SF 538 Coercing the legacy C locale to a UTF-8 based locale Alyssa Coghlan 3.7 SF 539 A New C-API for Thread-Local Storage in CPython Erik M. Bray, Masayuki Yamamoto 3.7 SF 540 Add a new UTF-8 Mode Victor Stinner 3.7 SF 544 Protocols: Structural subtyping (static duck typing) Ivan Levkivskyi, Jukka Lehtosalo, Łukasz Langa 3.8 SF 552 Deterministic pycs Benjamin Peterson 3.7 SF 553 Built-in breakpoint() Barry Warsaw 3.7 SF 557 Data Classes Eric V. Smith 3.7 SF 560 Core support for typing module and generic types Ivan Levkivskyi 3.7 SF 561 Distributing and Packaging Type Information Emma Harper Smith 3.7 SF 562 Module __getattr__ and __dir__ Ivan Levkivskyi 3.7 SF 564 Add new time functions with nanosecond resolution Victor Stinner 3.7 SF 565 Show DeprecationWarning in __main__ Alyssa Coghlan 3.7 SF 566 Metadata for Python Software Packages 2.1 Dustin Ingram 3.x SF 567 Context Variables Yury Selivanov 3.7 SF 570 Python Positional-Only Parameters Larry Hastings, Pablo Galindo Salgado, Mario Corchero, Eric N. Vander Weele 3.8 SF 572 Assignment Expressions Chris Angelico, Tim Peters, Guido van Rossum 3.8 SF 573 Module State Access from C Extension Methods Petr Viktorin, Alyssa Coghlan, Eric Snow, Marcel Plch 3.9 SF 574 Pickle protocol 5 with out-of-band data Antoine Pitrou 3.8 SF 578 Python Runtime Audit Hooks Steve Dower 3.8 SF 584 Add Union Operators To dict Steven D’Aprano, Brandt Bucher 3.9 SF 585 Type Hinting Generics In Standard Collections Łukasz Langa 3.9 SF 586 Literal Types Michael Lee, Ivan Levkivskyi, Jukka Lehtosalo 3.8 SF 587 Python Initialization Configuration Victor Stinner, Alyssa Coghlan 3.8 SF 589 TypedDict: Type Hints for Dictionaries with a Fixed Set of Keys Jukka Lehtosalo 3.8 SF 590 Vectorcall: a fast calling protocol for CPython Mark Shannon, Jeroen Demeyer 3.8 SF 591 Adding a final qualifier to typing Michael J. Sullivan, Ivan Levkivskyi 3.8 SF 592 Adding “Yank” Support to the Simple API Donald Stufft SF 593 Flexible function and variable annotations Till Varoquaux, Konstantin Kashin 3.9 SF 594 Removing dead batteries from the standard library Christian Heimes, Brett Cannon 3.11 SF 597 Add optional EncodingWarning Inada Naoki 3.10 SF 600 Future ‘manylinux’ Platform Tags for Portable Linux Built Distributions Nathaniel J. Smith, Thomas Kluyver SF 604 Allow writing union types as X | Y Philippe PRADOS, Maggie Moss 3.10 SF 610 Recording the Direct URL Origin of installed distributions Stéphane Bidoul, Chris Jerdonek SF 612 Parameter Specification Variables Mark Mendoza 3.10 SF 613 Explicit Type Aliases Shannon Zhu 3.10 SF 614 Relaxing Grammar Restrictions On Decorators Brandt Bucher 3.9 SF 615 Support for the IANA Time Zone Database in the Standard Library Paul Ganssle 3.9 SF 616 String methods to remove prefixes and suffixes Dennis Sweeney 3.9 SF 617 New PEG parser for CPython Guido van Rossum, Pablo Galindo Salgado, Lysandros Nikolaou 3.9 SF 618 Add Optional Length-Checking To zip Brandt Bucher 3.10 SF 621 Storing project metadata in pyproject.toml Brett Cannon, Dustin Ingram, Paul Ganssle, Pradyun Gedam, Sébastien Eustace, Thomas Kluyver, Tzu-ping Chung SF 623 Remove wstr from Unicode Inada Naoki 3.10 SF 624 Remove Py_UNICODE encoder APIs Inada Naoki 3.11 SF 625 Filename of a Source Distribution Tzu-ping Chung, Paul Moore SF 626 Precise line numbers for debugging and other tools. Mark Shannon 3.10 SF 627 Recording installed projects Petr Viktorin SF 628 Add math.tau Alyssa Coghlan 3.6 SF 629 Versioning PyPI’s Simple API Donald Stufft SF 632 Deprecate distutils module Steve Dower 3.10 SF 634 Structural Pattern Matching: Specification Brandt Bucher, Guido van Rossum 3.10 SF 639 Improving License Clarity with Better Package Metadata Philippe Ombredanne, C.A.M. Gerlach, Karolina Surma SF 643 Metadata for Package Source Distributions Paul Moore SF 644 Require OpenSSL 1.1.1 or newer Christian Heimes 3.10 SF 646 Variadic Generics Mark Mendoza, Matthew Rahtz, Pradeep Kumar Srinivasan, Vincent Siles 3.11 SF 647 User-Defined Type Guards Eric Traut 3.10 SF 649 Deferred Evaluation Of Annotations Using Descriptors Larry Hastings 3.14 SF 652 Maintaining the Stable ABI Petr Viktorin 3.10 SF 654 Exception Groups and except* Irit Katriel, Yury Selivanov, Guido van Rossum 3.11 SF 655 Marking individual TypedDict items as required or potentially-missing David Foster 3.11 SF 656 Platform Tag for Linux Distributions Using Musl Tzu-ping Chung SF 657 Include Fine Grained Error Locations in Tracebacks Pablo Galindo Salgado, Batuhan Taskaya, Ammar Askar 3.11 SF 660 Editable installs for pyproject.toml based builds (wheel based) Daniel Holth, Stéphane Bidoul SF 667 Consistent views of namespaces Mark Shannon, Tian Gao 3.13 SF 669 Low Impact Monitoring for CPython Mark Shannon 3.12 SF 670 Convert macros to functions in the Python C API Erlend Egeberg Aasland, Victor Stinner 3.11 SF 673 Self Type Pradeep Kumar Srinivasan, James Hilton-Balfe 3.11 SF 675 Arbitrary Literal String Type Pradeep Kumar Srinivasan, Graham Bleaney 3.11 SF 678 Enriching Exceptions with Notes Zac Hatfield-Dodds 3.11 SF 680 tomllib: Support for Parsing TOML in the Standard Library Taneli Hukkinen, Shantanu Jain 3.11 SF 681 Data Class Transforms Erik De Bonte, Eric Traut 3.11 SF 682 Format Specifier for Signed Zero John Belmonte 3.11 SF 683 Immortal Objects, Using a Fixed Refcount Eric Snow, Eddie Elizondo 3.12 SF 684 A Per-Interpreter GIL Eric Snow 3.12 SF 685 Comparison of extra names for optional distribution dependencies Brett Cannon SF 688 Making the buffer protocol accessible in Python Jelle Zijlstra 3.12 SF 689 Unstable C API tier Petr Viktorin 3.12 SF 692 Using TypedDict for more precise **kwargs typing Franek Magiera 3.12 SF 695 Type Parameter Syntax Eric Traut 3.12 SF 696 Type Defaults for Type Parameters James Hilton-Balfe 3.13 SF 697 Limited C API for Extending Opaque Types Petr Viktorin 3.12 SF 698 Override Decorator for Static Typing Steven Troxler, Joshua Xu, Shannon Zhu 3.12 SF 700 Additional Fields for the Simple API for Package Indexes Paul Moore SF 702 Marking deprecations using the type system Jelle Zijlstra 3.13 SF 705 TypedDict: Read-only items Alice Purcell 3.13 SF 706 Filter for tarfile.extractall Petr Viktorin 3.12 SF 709 Inlined comprehensions Carl Meyer 3.12 SF 715 Disabling bdist_egg distribution uploads on PyPI William Woodruff SF 721 Using tarfile.data_filter for source distribution extraction Petr Viktorin 3.12 SF 723 Inline script metadata Ofek Lev SF 730 Adding iOS as a supported platform Russell Keith-Magee 3.13 SF 734 Multiple Interpreters in the Stdlib Eric Snow 3.14 SF 735 Dependency Groups in pyproject.toml Stephen Rosen SF 737 C API to format a type fully qualified name Victor Stinner 3.13 SF 738 Adding Android as a supported platform Malcolm Smith 3.13 SF 740 Index support for digital attestations William Woodruff, Facundo Tuesca, Dustin Ingram SF 741 Python Configuration C API Victor Stinner 3.14 SF 742 Narrowing types with TypeIs Jelle Zijlstra 3.13 SF 749 Implementing PEP 649 Jelle Zijlstra 3.14 SF 750 Template Strings Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck 3.14 SF 751 A file format to record Python dependencies for installation reproducibility Brett Cannon SF 757 C API to import-export Python integers Sergey B Kirpichev, Victor Stinner 3.14 SF 758 Allow except and except* expressions without parentheses Pablo Galindo Salgado, Brett Cannon 3.14 SF 765 Disallow return/break/continue that exit a finally block Irit Katriel, Alyssa Coghlan 3.14 SF 768 Safe external debugger interface for CPython Pablo Galindo Salgado, Matt Wozniski, Ivona Stojanovic 3.14 SF 779 Criteria for supported status for free-threaded Python Thomas Wouters, Matt Page, Sam Gross 3.14 SF 782 Add PyBytesWriter C API Victor Stinner 3.15 SF 784 Adding Zstandard to the standard library Emma Harper Smith 3.14 SF 791 math.integer — submodule for integer-specific mathematics functions Neil Girdhar, Sergey B Kirpichev, Tim Peters, Serhiy Storchaka 3.15 SF 792 Project status markers in the simple index William Woodruff, Facundo Tuesca SF 3101 Advanced String Formatting Talin 3.0 SF 3102 Keyword-Only Arguments Talin 3.0 SF 3104 Access to Names in Outer Scopes Ka-Ping Yee 3.0 SF 3105 Make print a function Georg Brandl 3.0 SF 3106 Revamping dict.keys(), .values() and .items() Guido van Rossum 3.0 SF 3107 Function Annotations Collin Winter, Tony Lownds 3.0 SF 3108 Standard Library Reorganization Brett Cannon 3.0 SF 3109 Raising Exceptions in Python 3000 Collin Winter 3.0 SF 3110 Catching Exceptions in Python 3000 Collin Winter 3.0 SF 3111 Simple input built-in in Python 3000 Andre Roberge 3.0 SF 3112 Bytes literals in Python 3000 Jason Orendorff 3.0 SF 3113 Removal of Tuple Parameter Unpacking Brett Cannon 3.0 SF 3114 Renaming iterator.next() to iterator.__next__() Ka-Ping Yee 3.0 SF 3115 Metaclasses in Python 3000 Talin 3.0 SF 3116 New I/O Daniel Stutzbach, Guido van Rossum, Mike Verdone 3.0 SF 3118 Revising the buffer protocol Travis Oliphant, Carl Banks 3.0 SF 3119 Introducing Abstract Base Classes Guido van Rossum, Talin 3.0 SF 3120 Using UTF-8 as the default source encoding Martin von Löwis 3.0 SF 3121 Extension Module Initialization and Finalization Martin von Löwis 3.0 SF 3123 Making PyObject_HEAD conform to standard C Martin von Löwis 3.0 SF 3127 Integer Literal Support and Syntax Patrick Maupin 3.0 SF 3129 Class Decorators Collin Winter 3.0 SF 3131 Supporting Non-ASCII Identifiers Martin von Löwis 3.0 SF 3132 Extended Iterable Unpacking Georg Brandl 3.0 SF 3134 Exception Chaining and Embedded Tracebacks Ka-Ping Yee 3.0 SF 3135 New Super Calvin Spealman, Tim Delaney, Lie Ryan 3.0 SF 3137 Immutable Bytes and Mutable Buffer Guido van Rossum 3.0 SF 3138 String representation in Python 3000 Atsuo Ishimoto 3.0 SF 3141 A Type Hierarchy for Numbers Jeffrey Yasskin 3.0 SF 3144 IP Address Manipulation Library for the Python Standard Library Peter Moody 3.3 SF 3147 PYC Repository Directories Barry Warsaw 3.2 SF 3148 futures - execute computations asynchronously Brian Quinlan 3.2 SF 3149 ABI version tagged .so files Barry Warsaw 3.2 SF 3151 Reworking the OS and IO exception hierarchy Antoine Pitrou 3.3 SF 3154 Pickle protocol version 4 Antoine Pitrou 3.4 SF 3155 Qualified name for classes and functions Antoine Pitrou 3.3 SF 3156 Asynchronous IO Support Rebooted: the “asyncio” Module Guido van Rossum 3.3 Historical Meta-PEPs and Informational PEPs PEP Title Authors PS 5 Guidelines for Language Evolution Paul Prescod PS 6 Bug Fix Releases Aahz, Anthony Baxter IF 160 Python 1.6 Release Schedule Fred L. Drake, Jr. 1.6 IF 200 Python 2.0 Release Schedule Jeremy Hylton 2.0 IF 226 Python 2.1 Release Schedule Jeremy Hylton 2.1 IF 251 Python 2.2 Release Schedule Barry Warsaw, Guido van Rossum 2.2 IF 283 Python 2.3 Release Schedule Guido van Rossum 2.3 IF 320 Python 2.4 Release Schedule Barry Warsaw, Raymond Hettinger, Anthony Baxter 2.4 PF 347 Migrating the Python CVS to Subversion Martin von Löwis IF 356 Python 2.5 Release Schedule Neal Norwitz, Guido van Rossum, Anthony Baxter 2.5 PF 360 Externally Maintained Packages Brett Cannon IF 361 Python 2.6 and 3.0 Release Schedule Neal Norwitz, Barry Warsaw 2.6, 3.0 IF 373 Python 2.7 Release Schedule Benjamin Peterson 2.7 PF 374 Choosing a distributed VCS for the Python project Brett Cannon, Stephen J. Turnbull, Alexandre Vassalotti, Barry Warsaw, Dirkjan Ochtman IF 375 Python 3.1 Release Schedule Benjamin Peterson 3.1 PF 385 Migrating from Subversion to Mercurial Dirkjan Ochtman, Antoine Pitrou, Georg Brandl IF 392 Python 3.2 Release Schedule Georg Brandl 3.2 IF 398 Python 3.3 Release Schedule Georg Brandl 3.3 IF 404 Python 2.8 Un-release Schedule Barry Warsaw 2.8 IF 429 Python 3.4 Release Schedule Larry Hastings 3.4 PS 438 Transitioning to release-file hosting on PyPI Holger Krekel, Carl Meyer PF 449 Removal of the PyPI Mirror Auto Discovery and Naming Scheme Donald Stufft PF 464 Removal of the PyPI Mirror Authenticity API Donald Stufft PF 470 Removing External Hosting Support on PyPI Donald Stufft IF 478 Python 3.5 Release Schedule Larry Hastings 3.5 IF 494 Python 3.6 Release Schedule Ned Deily 3.6 PF 512 Migrating from hg.python.org to GitHub Brett Cannon IF 537 Python 3.7 Release Schedule Ned Deily 3.7 PF 541 Package Index Name Retention Łukasz Langa IF 569 Python 3.8 Release Schedule Łukasz Langa 3.8 PF 581 Using GitHub Issues for CPython Mariatta IF 596 Python 3.9 Release Schedule Łukasz Langa 3.9 PF 3000 Python 3000 Guido van Rossum PF 3002 Procedure for Backwards-Incompatible Changes Steven Bethard PF 3003 Python Language Moratorium Brett Cannon, Jesse Noller, Guido van Rossum PF 3099 Things that will Not Change in Python 3000 Georg Brandl PF 3100 Miscellaneous Python 3.0 Plans Brett Cannon PF 8001 Python Governance Voting Process Brett Cannon, Christian Heimes, Donald Stufft, Eric Snow, Gregory P. Smith, Łukasz Langa, Mariatta, Nathaniel J. Smith, Pablo Galindo Salgado, Raymond Hettinger, Tal Einat, Tim Peters, Zachary Ware Deferred PEPs (postponed pending further research or updates) PEP Title Authors SD 213 Attribute Access Handlers Paul Prescod 2.1 SD 219 Stackless Python Gordon McMillan 2.1 SD 222 Web Library Enhancements A.M. Kuchling 2.1 SD 233 Python Online Help Paul Prescod 2.1 SD 267 Optimized Access to Module Namespaces Jeremy Hylton 2.2 SD 269 Pgen Module for Python Jonathan Riehl 2.2 SD 280 Optimizing access to globals Guido van Rossum 2.3 SD 286 Enhanced Argument Tuples Martin von Löwis 2.3 SD 312 Simple Implicit Lambda Roman Suzi, Alex Martelli 2.4 SD 316 Programming by Contract for Python Terence Way SD 323 Copyable Iterators Alex Martelli 2.5 SD 337 Logging Usage in the Standard Library Michael P. Dubner 2.5 SD 368 Standard image protocol and class Lino Mastrodomenico 2.6, 3.0 SD 400 Deprecate codecs.StreamReader and codecs.StreamWriter Victor Stinner 3.3 SD 403 General purpose decorator clause (aka “@in” clause) Alyssa Coghlan 3.4 PD 407 New release cycle and introducing long-term support versions Antoine Pitrou, Georg Brandl, Barry Warsaw SD 419 Protecting cleanup statements from interruptions Paul Colomiets 3.3 ID 423 Naming conventions and recipes related to packaging Benoit Bryon ID 444 Python Web3 Interface Chris McDonough, Armin Ronacher SD 447 Add __getdescriptor__ method to metaclass Ronald Oussoren SD 491 The Wheel Binary Package Format 1.9 Daniel Holth SD 499 python -m foo should also bind ‘foo’ in sys.modules Cameron Simpson, Chris Angelico, Joseph Jevnik 3.10 SD 505 None-aware operators Mark E. Haase, Steve Dower 3.8 SD 532 A circuit breaking protocol and binary operators Alyssa Coghlan, Mark E. Haase 3.8 SD 533 Deterministic cleanup for iterators Nathaniel J. Smith SD 534 Improved Errors for Missing Standard Library Modules Tomáš Orsava, Petr Viktorin, Alyssa Coghlan SD 535 Rich comparison chaining Alyssa Coghlan 3.8 SD 547 Running extension modules using the -m option Marcel Plch, Petr Viktorin 3.7 SD 556 Threaded garbage collection Antoine Pitrou 3.7 SD 568 Generator-sensitivity for Context Variables Nathaniel J. Smith 3.8 SD 661 Sentinel Values Tal Einat SD 674 Disallow using macros as l-values Victor Stinner 3.12 SD 774 Removing the LLVM requirement for JIT builds Savannah Ostrowski 3.14 SD 778 Supporting Symlinks in Wheels Emma Harper Smith SD 787 Safer subprocess usage using t-strings Nick Humrich, Alyssa Coghlan 3.15 SD 3124 Overloading, Generic Functions, Interfaces, and Adaptation Phillip J. Eby SD 3143 Standard daemon process library Ben Finney 3.x SD 3150 Statement local namespaces (aka “given” clause) Alyssa Coghlan 3.4 Rejected, Superseded, and Withdrawn PEPs PEP Title Authors PW 3 Guidelines for Handling Bug Reports Jeremy Hylton PW 9 Sample Plaintext PEP Template Barry Warsaw PW 42 Feature Requests Jeremy Hylton IS 102 Doing Python Micro Releases Anthony Baxter, Barry Warsaw, Guido van Rossum IW 103 Collecting information about git Oleg Broytman SR 204 Range Literals Thomas Wouters 2.0 IW 206 Python Advanced Library A.M. Kuchling SW 209 Multi-dimensional Arrays Paul Barrett, Travis Oliphant 2.2 SR 210 Decoupling the Interpreter Loop David Ascher 2.1 SR 211 Adding A New Outer Product Operator Greg Wilson 2.1 SR 212 Loop Counter Iteration Peter Schneider-Kamp 2.1 SS 215 String Interpolation Ka-Ping Yee 2.1 IW 216 Docstring Format Moshe Zadka IR 220 Coroutines, Generators, Continuations Gordon McMillan SR 224 Attribute Docstrings Marc-André Lemburg 2.1 SR 225 Elementwise/Objectwise Operators Huaiyu Zhu, Gregory Lielens 2.1 SW 228 Reworking Python’s Numeric Model Moshe Zadka, Guido van Rossum SR 231 __findattr__() Barry Warsaw 2.1 SR 239 Adding a Rational Type to Python Christopher A. Craig, Moshe Zadka 2.2 SR 240 Adding a Rational Literal to Python Christopher A. Craig, Moshe Zadka 2.2 SS 241 Metadata for Python Software Packages A.M. Kuchling SW 242 Numeric Kinds Paul F. Dubois 2.2 SW 243 Module Repository Upload Mechanism Sean Reifschneider 2.1 SR 244 The directive statement Martin von Löwis 2.1 SR 245 Python Interface Syntax Michel Pelletier 2.2 SR 246 Object Adaptation Alex Martelli, Clark C. Evans 2.5 SR 254 Making Classes Look More Like Types Guido van Rossum 2.2 SR 256 Docstring Processing System Framework David Goodger SR 258 Docutils Design Specification David Goodger SR 259 Omit printing newline after newline Guido van Rossum 2.2 SR 262 A Database of Installed Python Packages A.M. Kuchling SR 265 Sorting Dictionaries by Value Grant Griffin 2.2 SW 266 Optimizing Global Variable/Attribute Access Skip Montanaro 2.3 SR 268 Extended HTTP functionality and WebDAV Greg Stein 2.x SR 270 uniq method for list objects Jason Petrone 2.2 SR 271 Prefixing sys.path by command line option Frédéric B. Giacometti 2.2 SR 275 Switching on Multiple Values Marc-André Lemburg 2.6 SR 276 Simple Iterator for ints Jim Althoff 2.3 SR 281 Loop Counter Iteration with range and xrange Magnus Lie Hetland 2.3 SR 284 Integer for-loops David Eppstein, Gregory Ewing 2.3 SW 288 Generators Attributes and Exceptions Raymond Hettinger 2.5 IS 291 Backward Compatibility for the Python 2 Standard Library Neal Norwitz 2.3 SR 294 Type Names in the types Module Oren Tirosh 2.5 SR 295 Interpretation of multiline string constants Stepan Koltsov 3.0 SW 296 Adding a bytes Object Type Scott Gilbert 2.3 SR 297 Support for System Upgrades Marc-André Lemburg 2.6 SW 298 The Locked Buffer Interface Thomas Heller 2.3 SR 299 Special __main__() function in modules Jeff Epler 2.3 SR 303 Extend divmod() for Multiple Divisors Thomas Bellman 2.3 SW 304 Controlling Generation of Bytecode Files Skip Montanaro IW 306 How to Change Python’s Grammar Michael Hudson, Jack Diederich, Alyssa Coghlan, Benjamin Peterson SR 310 Reliable Acquisition/Release Pairs Michael Hudson, Paul Moore 2.4 SR 313 Adding Roman Numeral Literals to Python Mike Meyer 2.4 SS 314 Metadata for Python Software Packages 1.1 A.M. Kuchling, Richard Jones 2.5 SR 315 Enhanced While Loop Raymond Hettinger, W Isaac Carroll 2.5 SR 317 Eliminate Implicit Exception Instantiation Steven Taschuk 2.4 SR 319 Python Synchronize/Asynchronize Block Michel Pelletier 2.4 SW 321 Date/Time Parsing and Formatting A.M. Kuchling 2.4 SR 325 Resource-Release Support for Generators Samuele Pedroni 2.4 SR 326 A Case for Top and Bottom Values Josiah Carlson, Terry Reedy 2.4 SR 329 Treating Builtins as Constants in the Standard Library Raymond Hettinger 2.4 SR 330 Python Bytecode Verification Michel Pelletier 2.6 SR 332 Byte vectors and String/Unicode Unification Skip Montanaro 2.5 SW 334 Simple Coroutines via SuspendIteration Clark C. Evans 3.0 SR 335 Overloadable Boolean Operators Gregory Ewing 3.3 SR 336 Make None Callable Andrew McClelland IW 339 Design of the CPython Compiler Brett Cannon SR 340 Anonymous Block Statements Guido van Rossum SS 344 Exception Chaining and Embedded Tracebacks Ka-Ping Yee 2.5 SS 345 Metadata for Python Software Packages 1.2 Richard Jones 2.7 SW 346 User Defined (“with”) Statements Alyssa Coghlan 2.5 SR 348 Exception Reorganization for Python 3.0 Brett Cannon SR 349 Allow str() to return unicode strings Neil Schemenauer 2.5 IR 350 Codetags Micah Elliott SR 351 The freeze protocol Barry Warsaw 2.5 SS 354 Enumerations in Python Ben Finney 2.6 SR 355 Path - Object oriented filesystem paths Björn Lindqvist 2.5 SW 359 The “make” Statement Steven Bethard 2.6 SR 363 Syntax For Dynamic Attribute Access Ben North SW 364 Transitioning to the Py3K Standard Library Barry Warsaw 2.6 SR 365 Adding the pkg_resources module Phillip J. Eby SS 367 New Super Calvin Spealman, Tim Delaney 2.6 SW 369 Post import hooks Christian Heimes 2.6, 3.0 SR 377 Allow __enter__() methods to skip the statement body Alyssa Coghlan 2.7, 3.1 SW 379 Adding an Assignment Expression Jervis Whitley 2.7, 3.2 SW 381 Mirroring infrastructure for PyPI Tarek Ziadé, Martin von Löwis SR 382 Namespace Packages Martin von Löwis 3.2 SS 386 Changing the version comparison module in Distutils Tarek Ziadé SR 390 Static metadata for Distutils Tarek Ziadé 2.7, 3.2 SW 395 Qualified Names for Modules Alyssa Coghlan 3.4 IW 396 Module Version Numbers Barry Warsaw PR 401 BDFL Retirement Barry Warsaw, Brett Cannon SR 402 Simplified Package Layout and Partitioning Phillip J. Eby 3.3 SW 406 Improved Encapsulation of Import State Alyssa Coghlan, Greg Slodkowicz 3.4 SR 408 Standard library __preview__ package Alyssa Coghlan, Eli Bendersky 3.3 SR 410 Use decimal.Decimal type for timestamps Victor Stinner 3.3 IS 411 Provisional packages in the Python standard library Alyssa Coghlan, Eli Bendersky 3.3 PW 413 Faster evolution of the Python Standard Library Alyssa Coghlan SR 416 Add a frozendict builtin type Victor Stinner 3.3 SW 422 Simpler customisation of class creation Alyssa Coghlan, Daniel Urban 3.5 IW 426 Metadata for Python Software Packages 2.0 Alyssa Coghlan, Daniel Holth, Donald Stufft SS 431 Time zone support improvements Lennart Regebro SW 432 Restructuring the CPython startup sequence Alyssa Coghlan, Victor Stinner, Eric Snow SS 433 Easier suppression of file descriptor inheritance Victor Stinner 3.4 SR 437 A DSL for specifying signatures, annotations and argument converters Stefan Krah 3.4 SR 439 Inclusion of implicit pip bootstrap in Python installation Richard Jones 3.4 SR 455 Adding a key-transforming dictionary to collections Antoine Pitrou 3.5 SW 459 Standard Metadata Extensions for Python Software Packages Alyssa Coghlan SW 460 Add binary interpolation and formatting Antoine Pitrou 3.5 PW 462 Core development workflow automation for CPython Alyssa Coghlan SR 463 Exception-catching expressions Chris Angelico 3.5 SW 469 Migration of dict iteration code to Python 3 Alyssa Coghlan 3.5 SR 472 Support for indexing with keyword arguments Stefano Borini, Joseph Martinot-Lagarde 3.6 SR 473 Adding structured data to built-in exceptions Sebastian Kreft PW 474 Creating forge.python.org Alyssa Coghlan PW 481 Migrate CPython to Git, Github, and Phabricator Donald Stufft SR 490 Chain exceptions at C level Victor Stinner 3.6 IR 496 Environment Markers James Polley PR 497 A standard mechanism for backward compatibility Ed Schofield SR 500 A protocol for delegating datetime methods to their tzinfo implementations Alexander Belopolsky, Tim Peters SW 501 General purpose template literal strings Alyssa Coghlan, Nick Humrich 3.12 IR 502 String Interpolation - Extended Discussion Mike G. Miller 3.6 SW 504 Using the System RNG by default Alyssa Coghlan 3.6 PR 507 Migrate CPython to Git and GitLab Barry Warsaw SS 509 Add a private version to dict Victor Stinner 3.6 SR 510 Specialize functions with guards Victor Stinner 3.6 SR 511 API for code transformers Victor Stinner 3.6 IS 513 A Platform Tag for Portable Linux Built Distributions Robert T. McGibbon, Nathaniel J. Smith SR 516 Build system abstraction for pip/conda etc Robert Collins, Nathaniel J. Smith SW 521 Managing global context via ‘with’ blocks in generators and coroutines Nathaniel J. Smith 3.6 SR 522 Allow BlockingIOError in security sensitive APIs Alyssa Coghlan, Nathaniel J. Smith 3.6 SW 531 Existence checking operators Alyssa Coghlan 3.7 SW 536 Final Grammar for Literal String Interpolation Philipp Angerer 3.7 SR 542 Dot Notation Assignment In Function Header Markus Meskanen SW 543 A Unified TLS API for Python Cory Benfield, Christian Heimes 3.7 SR 546 Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7 Victor Stinner, Cory Benfield 2.7 SR 548 More Flexible Loop Control R David Murray 3.7 SR 549 Instance Descriptors Larry Hastings 3.7 SW 550 Execution Context Yury Selivanov, Elvis Pranskevichus 3.7 IW 551 Security transparency in the Python runtime Steve Dower 3.7 SS 554 Multiple Interpreters in the Stdlib Eric Snow 3.13 SW 555 Context-local variables (contextvars) Koos Zevenhoven 3.7 SW 558 Defined semantics for locals() Alyssa Coghlan 3.13 SR 559 Built-in noop() Barry Warsaw 3.7 SS 563 Postponed Evaluation of Annotations Łukasz Langa 3.7 IS 571 The manylinux2010 Platform Tag Mark Williams, Geoffrey Thomas, Thomas Kluyver SW 575 Unifying function/method classes Jeroen Demeyer 3.8 SW 576 Rationalize Built-in function classes Mark Shannon 3.8 SW 577 Augmented Assignment Expressions Alyssa Coghlan 3.8 SR 580 The C call protocol Jeroen Demeyer 3.8 SR 582 Python local packages directory Kushal Das, Steve Dower, Donald Stufft, Alyssa Coghlan 3.12 IW 583 A Concurrency Memory Model for Python Jeffrey Yasskin IW 595 Improving bugs.python.org Ezio Melotti, Berker Peksag IW 598 Introducing incremental feature releases Alyssa Coghlan 3.9 IS 599 The manylinux2014 Platform Tag Dustin Ingram SR 601 Forbid return/break/continue breaking out of finally Damien George, Batuhan Taskaya 3.8 IR 605 A rolling feature release stream for CPython Steve Dower, Alyssa Coghlan 3.9 SR 606 Python Compatibility Version Victor Stinner 3.9 SR 608 Coordinated Python release Miro Hrončok, Victor Stinner 3.9 SW 611 The one million limit Mark Shannon SW 620 Hide implementation details from the C API Victor Stinner 3.12 SS 622 Structural Pattern Matching Brandt Bucher, Daniel F Moisset, Tobias Kohn, Ivan Levkivskyi, Guido van Rossum, Talin 3.10 SS 631 Dependency specification in pyproject.toml based on PEP 508 Ofek Lev SR 633 Dependency specification in pyproject.toml using an exploded TOML table Laurie Opperman, Arun Babu Neelicattu SR 637 Support for indexing with keyword arguments Stefano Borini 3.10 SR 640 Unused variable syntax Thomas Wouters 3.10 SR 641 Using an underscore in the version portion of Python 3.10 compatibility tags Brett Cannon, Steve Dower, Barry Warsaw 3.10 SR 642 Explicit Pattern Syntax for Structural Pattern Matching Alyssa Coghlan 3.10 SW 645 Allow writing optional types as x? Maggie Moss SR 648 Extensible customizations of the interpreter at startup Mario Corchero 3.11 SW 650 Specifying Installer Requirements for Python Projects Vikram Jayanthi, Dustin Ingram, Brett Cannon SR 651 Robust Stack Overflow Handling Mark Shannon SR 662 Editable installs via virtual wheels Bernát Gábor IR 663 Standardizing Enum str(), repr(), and format() behaviors Ethan Furman 3.11 SR 665 A file format to list Python dependencies for reproducibility of an application Brett Cannon, Pradyun Gedam, Tzu-ping Chung SR 666 Reject Foolish Indentation Laura Creighton 2.2 SR 677 Callable Type Syntax Steven Troxler, Pradeep Kumar Srinivasan 3.11 SR 679 New assert statement syntax with parentheses Pablo Galindo Salgado, Stan Ulbrych 3.15 SR 690 Lazy Imports Germán Méndez Bravo, Carl Meyer 3.12 SW 704 Require virtual environments by default for package installers Pradyun Gedam SR 707 A simplified signature for __exit__ and __aexit__ Irit Katriel 3.12 SR 712 Adding a “converter” parameter to dataclasses.field Joshua Cannon 3.13 SR 713 Callable Modules Amethyst Reese 3.12 SR 722 Dependency specification for single-file scripts Paul Moore SW 724 Stricter Type Guards Rich Chiodo, Eric Traut, Erik De Bonte 3.13 SR 726 Module __setattr__ and __delattr__ Sergey B Kirpichev 3.13 SW 727 Documentation in Annotated Metadata Sebastián Ramírez 3.13 SR 736 Shorthand syntax for keyword arguments at invocation Joshua Bambrick, Chris Angelico 3.14 SR 754 IEEE 754 Floating Point Special Values Gregory R. Warnes 2.3 SW 756 Add PyUnicode_Export() and PyUnicode_Import() C functions Victor Stinner 3.14 SW 759 External Wheel Hosting Barry Warsaw, Emma Harper Smith SW 760 No More Bare Excepts Pablo Galindo Salgado, Brett | 2026-01-13T08:49:04 |
https://dev.to/askrishnapravin/for-loop-vs-map-for-making-multiple-api-calls-3lhd#comment-1gid7 | for loop vs .map() for making multiple API calls - 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 Krishna Pravin Posted on May 14, 2020 • Edited on May 29, 2020 for loop vs .map() for making multiple API calls # javascript # api # async Promise / async-await is used for making API calls. const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/1` ) const todo = await response . json () console . log ( todo ) Enter fullscreen mode Exit fullscreen mode Assuming I have a list of ids of todo items and I want the title of all them then I shall use the below snippet inside an async function const todoIdList = [ 1 , 2 , 3 , 4 ] for ( const id of todoIdList ) { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) } Enter fullscreen mode Exit fullscreen mode This same can be written with any of these for , for...in , for...of loops. Assuming each API request arbitrarily takes 100ms exactly, the total time taken for getting the details of four todo items will have to be greater than 400ms if we use any of the above-mentioned loops. This execution time can be drastically reduced by using .map() . const todoIdList = [ 1 , 2 , 3 , 4 ] await Promise . all ( todoIdList . map ( async ( id ) => { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) }) ) Enter fullscreen mode Exit fullscreen mode Adding timers const todoIdList = [ 1 , 2 , 3 , 4 ] console . time ( ' for {} ' ); for ( const id of todoIdList ) { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) } console . timeEnd ( ' for {} ' ); console . time ( ' .map() ' ); await Promise . all ( todoIdList . map ( async ( id ) => { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) }) ) console . timeEnd ( ' .map() ' ); Enter fullscreen mode Exit fullscreen mode The Reason for loop for loop goes to the next iteration only after the whole block's execution is completed. In the above scenario only after both the promises(await) gets resolved , for loop moves to the next iteration and makes the API call for the next todo item. .map() .map() moves on to the next item as soon as a promise is returned . It does not wait until the promise is resolved. In the above scenario, .map() does not wait until the response for todo items comes from the server. It makes all the API calls one by one and for each API call it makes, a respective promise is returned. Promise.all waits until all of these promises are resolved. async/await is syntactic sugar for Promises It will be more clear if the same code is written without async/await const todoIdList = [ 1 , 2 , 3 , 4 ] console . time ( ' .map() ' ) Promise . all ( todoIdList . map ( id => { return new Promise (( resolve ) => { fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) . then ( response => { return new Promise (() => { response . json () . then ( todo => { console . log ( todo . title ) resolve () }) }) }) }) }) ) . then (() => { console . timeEnd ( ' .map() ' ); }) Enter fullscreen mode Exit fullscreen mode It is not possible to mimic the respective code for for loop by replacing async/await with Promises because, the control which triggers the next iteration will have to written within the .then() block. This piece of code will have to be created within the JS engine. All the snippets are working code, you can try it directly in the browser console. Note: snippets need to be enclosed within an async function except for the last one use Axios or any other suitable library if fetch is not available. Let me know if there is an even better and easy/short way of making API calls. Also, do not forget to mention any mistakes I've made or tips, suggestions to improve this content. Top comments (6) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Quinn Quinn Quinn Follow Joined Jun 28, 2021 • Jun 28 '21 Dropdown menu Copy link Hide Not really a fair comparison. Map is creating a new array of promises then asynchronously executing them. To do this with a for loop you would do something like this: const todoIdList = [1, 2, 3, 4] const promiseList = [] for (const id of todoIdList) { const response = fetch( https://jsonplaceholder.typicode.com/todos/${id} ) promiseList.push(response.json()) } const responses = Promise.all(promiseList) Like comment: Like comment: 5 likes Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Jul 26 '21 Dropdown menu Copy link Hide This approach looks good. Pushing the promises into an array within for loop will achieve concurrency. But when we have a need for more than one await inside the block, it will not work. In the above code, response.json() won't work because response is a promise, it won't have json() method. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Yogendra Yogendra Yogendra Follow Location Bengaluru, India Work Web Developer at LayerIV Joined Sep 25, 2020 • Jan 31 '21 Dropdown menu Copy link Hide This is quite great. But, could you tell me what is the optimum way to resolve multiple promises and get their statuses, as Promise.all() fails as soon as any of the Promise rejects? I heard of Promise.allSettled() but is only available in recent versions of ES. Thanks!! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Feb 9 '21 Dropdown menu Copy link Hide Shim: npmjs.com/package/promise.allsettled Polyfill: logic24by7.com/promise-allsettled-... Like comment: Like comment: Like Comment button Reply Collapse Expand Rajesh Moka Rajesh Moka Rajesh Moka Follow I am a front end developer. I like building stuff with react. Location India Work Front End Developer at Tata Consultancy Services Joined May 27, 2020 • Jan 20 '21 Dropdown menu Copy link Hide This is a great article. I had trouble understanding the last example without async await but with promises. I knew promise.all takes promises array as an argument, but why did we write promise in each fetch call? Can u explain a little Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Jan 29 '21 Dropdown menu Copy link Hide The last example(using promise) is the same as the previous one(using await). We have a promise inside fetch because parsing response as json response.json() returns a promise. For each API call, Promise.all() will first wait for the API call's response to arrive, and then it will wait for the json parsing to complete. When Promise.all takes an array of promises, it will wait for all the inner promises as well to get resolved. 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 Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 Trending on DEV Community Hot Top 7 Featured DEV Posts of the Week # top7 # discuss Stop Overengineering: How to Write Clean Code That Actually Ships 🚀 # discuss # javascript # programming # webdev If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://gg.forem.com/t/nintendoswitch | Nintendoswitch - Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close # nintendoswitch Follow Hide Portable Nintendo fun anywhere, anytime Create Post Older #nintendoswitch 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 IGN: Absolum Review Gaming News Gaming News Gaming News Follow Oct 9 '25 IGN: Absolum Review # pcgaming # nintendoswitch # indie # playstation Comments Add Comment 1 min read The Game Theorists: Game Theory: How DEADLY Is Donkey Kong's Punch? Gaming News Gaming News Gaming News Follow Oct 8 '25 The Game Theorists: Game Theory: How DEADLY Is Donkey Kong's Punch? # nintendo # nintendoswitch # retrogaming # pcgaming Comments Add Comment 1 min read IGN: Teenage Mutant Ninja Turtles: Splintered Fate - Official Free Update & Metalhead DLC Launch Trailer Gaming News Gaming News Gaming News Follow Sep 30 '25 IGN: Teenage Mutant Ninja Turtles: Splintered Fate - Official Free Update & Metalhead DLC Launch Trailer # pcgaming # playstation # xbox # nintendoswitch 2 reactions Comments Add Comment 1 min read IGN: Blood: Refreshed Supply - Official Announcement Trailer Gaming News Gaming News Gaming News Follow Sep 29 '25 IGN: Blood: Refreshed Supply - Official Announcement Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Resident Evil Requiem: Switch 2 Gameplay (Off-Screen) | TGS 2025 Gaming News Gaming News Gaming News Follow Sep 29 '25 IGN: Resident Evil Requiem: Switch 2 Gameplay (Off-Screen) | TGS 2025 # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: EA Sports FC 26 Review Gaming News Gaming News Gaming News Follow Sep 27 '25 IGN: EA Sports FC 26 Review # pcgaming # playstation # nintendoswitch # xbox Comments Add Comment 1 min read GameSpot: Hollow Knight: Silksong Review Gaming News Gaming News Gaming News Follow Sep 26 '25 GameSpot: Hollow Knight: Silksong Review # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Asus ROG Xbox Ally – The Final Preview Gaming News Gaming News Gaming News Follow Sep 26 '25 IGN: Asus ROG Xbox Ally – The Final Preview # xbox # pcgaming # nintendoswitch # steam Comments Add Comment 1 min read IGN: Animula Nook - Official Gameplay Trailer Gaming News Gaming News Gaming News Follow Sep 26 '25 IGN: Animula Nook - Official Gameplay Trailer # gamedev # pcgaming # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Formula Legends Review Gaming News Gaming News Gaming News Follow Sep 26 '25 IGN: Formula Legends Review # pcgaming # xbox # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Pokémon Legends: Z-A – The Final Preview Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Pokémon Legends: Z-A – The Final Preview # nintendo # nintendoswitch Comments Add Comment 1 min read GameSpot: Hyrule Warriors: Age of Imprisonment Is Adding A Lot More Depth To Combat Gaming News Gaming News Gaming News Follow Sep 25 '25 GameSpot: Hyrule Warriors: Age of Imprisonment Is Adding A Lot More Depth To Combat # nintendo # nintendoswitch # pcgaming # gamedev Comments Add Comment 1 min read IGN: Cyberpunk 2077: Ultimate Edition - Official ‘New Ways to Play’ Nintendo Switch 2 Trailer Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Cyberpunk 2077: Ultimate Edition - Official ‘New Ways to Play’ Nintendo Switch 2 Trailer # nintendo # nintendoswitch # pcgaming # playstation Comments Add Comment 1 min read IGN: The Adventures of Elliot: The Millennium Tales - Official TGS 2025 Trailer Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: The Adventures of Elliot: The Millennium Tales - Official TGS 2025 Trailer # gaming # nintendoswitch # playstation # xbox Comments Add Comment 1 min read IGN: Hollow Knight: Silksong Boss Fight - Cogwork Dancers (Choral Chambers) Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Hollow Knight: Silksong Boss Fight - Cogwork Dancers (Choral Chambers) # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Hades 2 Full Release: First 15 Minutes of Nintendo Switch 2 Gameplay (4K 60FPS) Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Hades 2 Full Release: First 15 Minutes of Nintendo Switch 2 Gameplay (4K 60FPS) # nintendo # nintendoswitch # pcgaming # indie Comments Add Comment 1 min read GameSpot: Resident Evil Requiem Gameplay Overview | Capcom Online Program TGS 2025 Gaming News Gaming News Gaming News Follow Sep 24 '25 GameSpot: Resident Evil Requiem Gameplay Overview | Capcom Online Program TGS 2025 # pcgaming # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Phoenix Wright Ace Attorney Trilogy - Official Update Trailer | TGS 2025 Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Phoenix Wright Ace Attorney Trilogy - Official Update Trailer | TGS 2025 # pcgaming # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Hades 2 Review Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Hades 2 Review # pcgaming # nintendoswitch # nintendo # indie Comments Add Comment 1 min read IGN: Monster Hunter Stories 3: Twisted Reflection - Official Release Date Trailer | TGS 2025 Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Monster Hunter Stories 3: Twisted Reflection - Official Release Date Trailer | TGS 2025 # nintendo # nintendoswitch # pcgaming # playstation Comments Add Comment 1 min read IGN: Final Fantasy Tactics: The Ivalice Chronicles Review Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Final Fantasy Tactics: The Ivalice Chronicles Review # playstation # xbox # pcgaming # nintendoswitch Comments Add Comment 1 min read IGN: Animula Nook - Official Reveal Trailer Gaming News Gaming News Gaming News Follow Sep 24 '25 IGN: Animula Nook - Official Reveal Trailer # gamedev # pcgaming # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Danganronpa 2x2 - Official Teaser Trailer Gaming News Gaming News Gaming News Follow Sep 21 '25 IGN: Danganronpa 2x2 - Official Teaser Trailer # nintendoswitch # playstation # xbox # steam Comments Add Comment 1 min read IGN: Hollow Knight: Silksong - How to Make It Through Bilewater Gaming News Gaming News Gaming News Follow Sep 20 '25 IGN: Hollow Knight: Silksong - How to Make It Through Bilewater # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Is Nintendo Switch 2 Off to a Good Start? - NVC Clips Gaming News Gaming News Gaming News Follow Sep 20 '25 IGN: Is Nintendo Switch 2 Off to a Good Start? - NVC Clips # nintendo # nintendoswitch # gamedev 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 Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/t/kotlin/page/4 | Kotlin Page 4 - 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 Kotlin Follow Hide a cross-platform, statically typed, general-purpose programming language with type inference Create Post Older #kotlin 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 SteadyFetch: A tiny Android SDK that refuses to let your downloads die Naman Anand Naman Anand Naman Anand Follow Nov 23 '25 SteadyFetch: A tiny Android SDK that refuses to let your downloads die # android # kotlin # opensource # networking Comments Add Comment 3 min read Resolvendo o desafio 509. Fibonacci Number Filipe Câncio Filipe Câncio Filipe Câncio Follow Nov 23 '25 Resolvendo o desafio 509. Fibonacci Number # leetcode # algorithms # kotlin # java Comments Add Comment 4 min read Semantic Typing We Ignore Vadym Yaroshchuk Vadym Yaroshchuk Vadym Yaroshchuk Follow Dec 24 '25 Semantic Typing We Ignore # kotlin # architecture # programming # codequality 21 reactions Comments 2 comments 18 min read Dagger 2.0 vs Hilt in Android: A Comprehensive Overview Love Garg Love Garg Love Garg Follow Nov 16 '25 Dagger 2.0 vs Hilt in Android: A Comprehensive Overview # dagger # hilt # kotlin # android Comments Add Comment 2 min read Building an Android Video Call Application with ZEGOCLOUD CallKit (Kotlin) Sandy Pradana Sandy Pradana Sandy Pradana Follow Dec 9 '25 Building an Android Video Call Application with ZEGOCLOUD CallKit (Kotlin) # kotlin # zegocloud # videocall # androiddev 1 reaction Comments 1 comment 7 min read Implementing Strictly Typed JsonRpc Method Calls in Kotlin Artem Artem Artem Follow Nov 16 '25 Implementing Strictly Typed JsonRpc Method Calls in Kotlin # kotlin # acp # jsonrpc # typesafe Comments Add Comment 10 min read (🐱-1-1; Drop) Media Preview and Converter with Kotlin Compose Multiplatform Felis Cato Felis Cato Felis Cato Follow Dec 20 '25 (🐱-1-1; Drop) Media Preview and Converter with Kotlin Compose Multiplatform # android # mobile # kotlin # devjournal Comments Add Comment 8 min read Mastering the R8 Metadata: Beyond the Stack Trace 🕵️♂️ Sivavishnu R Sivavishnu R Sivavishnu R Follow Dec 18 '25 Mastering the R8 Metadata: Beyond the Stack Trace 🕵️♂️ # android # r8 # proguard # kotlin Comments Add Comment 6 min read Code Generation vs. Reflection: A Build-Time Reliability Analysis Sivavishnu R Sivavishnu R Sivavishnu R Follow Dec 18 '25 Code Generation vs. Reflection: A Build-Time Reliability Analysis # kotlin # reflection # android # r8 Comments Add Comment 6 min read Introducing Pale Blue Spring Admin: auto-generated admin UI for Spring Boot RockAndNull RockAndNull RockAndNull Follow Nov 14 '25 Introducing Pale Blue Spring Admin: auto-generated admin UI for Spring Boot # kotlin # backend Comments Add Comment 2 min read 📐 Material 3 Adaptive: Implementing Window Size Classes in Kotlin Compose Marlon López Marlon López Marlon López Follow Nov 12 '25 📐 Material 3 Adaptive: Implementing Window Size Classes in Kotlin Compose # android # jetpackcompose # kotlin # materialdesign3 Comments Add Comment 2 min read I compared 17 Kotlin MVI libraries across 103 criteria - here are THE BEST 4 Nek.12 Nek.12 Nek.12 Follow Nov 24 '25 I compared 17 Kotlin MVI libraries across 103 criteria - here are THE BEST 4 # kotlin # mvi # architecture # android Comments Add Comment 23 min read Everyone Talks About Clean Architecture — No One Fixes the Data Layer Vaibhav Shakya Vaibhav Shakya Vaibhav Shakya Follow Dec 16 '25 Everyone Talks About Clean Architecture — No One Fixes the Data Layer # android # kotlin # cleanarchitecture # cybersecurity Comments Add Comment 1 min read Kotlin vs Go: The Developer Showdown That Won’t End CHILLICODE CHILLICODE CHILLICODE Follow Nov 10 '25 Kotlin vs Go: The Developer Showdown That Won’t End # go # kotlin # development # webdev Comments Add Comment 3 min read I achieved 0% ANR in my Android app. Spilling beans on how I did it - part 1 Nek.12 Nek.12 Nek.12 Follow Nov 9 '25 I achieved 0% ANR in my Android app. Spilling beans on how I did it - part 1 # android # anr # performance # kotlin Comments Add Comment 3 min read Android SaaS App with Subscriptions: Complete 2025 Guide krlz krlz krlz Follow Dec 13 '25 Android SaaS App with Subscriptions: Complete 2025 Guide # android # saas # kotlin # supabase 1 reaction Comments 1 comment 9 min read SilencioHardwareStore - Mobile App Bruno C Perez Bruno C Perez Bruno C Perez Follow Nov 6 '25 SilencioHardwareStore - Mobile App # kotlin # android # development # ai Comments Add Comment 2 min read suppa - one command to dive into the Android SDK Ken Koro Ken Koro Ken Koro Follow Dec 9 '25 suppa - one command to dive into the Android SDK # kotlin # mobile # opensource # firebase 1 reaction Comments Add Comment 1 min read How to load data in Kotlin with MVVM, MVI, Flow, Coroutines - COMPLETE Guide Nek.12 Nek.12 Nek.12 Follow Nov 4 '25 How to load data in Kotlin with MVVM, MVI, Flow, Coroutines - COMPLETE Guide # kotlin # android # coroutines # flow Comments Add Comment 15 min read I Built a Wear OS App in One Evening. Full Guide and All the Google API Pitfalls Nek.12 Nek.12 Nek.12 Follow Nov 4 '25 I Built a Wear OS App in One Evening. Full Guide and All the Google API Pitfalls # wearos # android # kotlin # compose Comments Add Comment 6 min read File Bucketer, a simple CLI tool to organize files into buckets Maksymilian Maksymilian Maksymilian Follow Nov 1 '25 File Bucketer, a simple CLI tool to organize files into buckets # kotlin # programming # cli Comments Add Comment 2 min read I built a “Play Store for GitHub releases” with Kotlin Multiplatform rainxchzed rainxchzed rainxchzed Follow Dec 2 '25 I built a “Play Store for GitHub releases” with Kotlin Multiplatform # android # kotlin # kotlinmultiplatform # linux 7 reactions Comments Add Comment 3 min read Is the Java ecosystem cursed? A dependency analysis perspective Tony Robalik Tony Robalik Tony Robalik Follow Nov 24 '25 Is the Java ecosystem cursed? A dependency analysis perspective # java # kotlin # gradle 18 reactions Comments 15 comments 8 min read Android Dev Hack: Windsurf > ChatGPT + Android Studio Switching Manuth Lochana Manuth Lochana Manuth Lochana Follow Nov 29 '25 Android Dev Hack: Windsurf > ChatGPT + Android Studio Switching # android # kotlin Comments 1 comment 1 min read Hacknight SmartFarm Project ALDO KIPYEGON ALDO KIPYEGON ALDO KIPYEGON Follow Oct 24 '25 Hacknight SmartFarm Project # showdev # sideprojects # android # kotlin Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://peps.python.org/pep-0272/ | PEP 272 – API for Block Encryption Algorithms v1.0 | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 272 Toggle light / dark / auto colour theme PEP 272 – API for Block Encryption Algorithms v1.0 Author : A.M. Kuchling <amk at amk.ca> Status : Final Type : Informational Created : 18-Sep-2001 Post-History : 17-Apr-2002, 29-May-2002 Table of Contents Abstract Introduction Specification References Changes Acknowledgements Copyright Abstract This document specifies a standard API for secret-key block encryption algorithms such as DES or Rijndael, making it easier to switch between different algorithms and implementations. Introduction Encryption algorithms transform their input data (called plaintext) in some way that is dependent on a variable key, producing ciphertext. The transformation can easily be reversed if and only if one knows the key. The key is a sequence of bits chosen from some very large space of possible keys. There are two classes of encryption algorithms: block ciphers and stream ciphers. Block ciphers encrypt multibyte inputs of a fixed size (frequently 8 or 16 bytes long), and can be operated in various feedback modes. The feedback modes supported in this specification are: Number Constant Description 1 MODE_ECB Electronic Code Book 2 MODE_CBC Cipher Block Chaining 3 MODE_CFB Cipher Feedback 5 MODE_OFB Output Feedback 6 MODE_CTR Counter These modes are to be implemented as described in NIST publication SP 800-38A [1] . Descriptions of the first three feedback modes can also be found in Bruce Schneier’s book Applied Cryptography [2] . (The numeric value 4 is reserved for MODE_PGP, a variant of CFB described in RFC 2440 : “OpenPGP Message Format”. This mode isn’t considered important enough to make it worth requiring it for all block encryption ciphers, though supporting it is a nice extra feature.) In a strict formal sense, stream ciphers encrypt data bit-by-bit; practically, stream ciphers work on a character-by-character basis. This PEP only aims at specifying an interface for block ciphers, though stream ciphers can support the interface described here by fixing ‘block_size’ to 1. Feedback modes also don’t make sense for stream ciphers, so the only reasonable feedback mode would be ECB mode. Specification Encryption modules can add additional functions, methods, and attributes beyond those described in this PEP, but all of the features described in this PEP must be present for a module to claim compliance with it. Secret-key encryption modules should define one function: new ( key , mode , [ IV ], ** kwargs ) Returns a ciphering object, using the secret key contained in the string ‘key’, and using the feedback mode ‘mode’, which must be one of the constants from the table above. If ‘mode’ is MODE_CBC or MODE_CFB, ‘IV’ must be provided and must be a string of the same length as the block size. Not providing a value of ‘IV’ will result in a ValueError exception being raised. Depending on the algorithm, a module may support additional keyword arguments to this function. Some keyword arguments are specified by this PEP, and modules are free to add additional keyword arguments. If a value isn’t provided for a given keyword, a secure default value should be used. For example, if an algorithm has a selectable number of rounds between 1 and 16, and 1-round encryption is insecure and 8-round encryption is believed secure, the default value for ‘rounds’ should be 8 or more. (Module implementors can choose a very slow but secure value, too, such as 16 in this example. This decision is left up to the implementor.) The following table lists keyword arguments defined by this PEP: Keyword Meaning counter Callable object that returns counter blocks (see below; CTR mode only) rounds Number of rounds of encryption to use segment_size Size of data and ciphertext segments, measured in bits (see below; CFB mode only) The Counter feedback mode requires a sequence of input blocks, called counters, that are used to produce the output. When ‘mode’ is MODE_CTR, the ‘counter’ keyword argument must be provided, and its value must be a callable object, such as a function or method. Successive calls to this callable object must return a sequence of strings that are of the length ‘block_size’ and that never repeats. (Appendix B of the NIST publication gives a way to generate such a sequence, but that’s beyond the scope of this PEP.) The CFB mode operates on segments of the plaintext and ciphertext that are ‘segment_size’ bits long. Therefore, when using this mode, the input and output strings must be a multiple of ‘segment_size’ bits in length. ‘segment_size’ must be an integer between 1 and block_size*8, inclusive. (The factor of 8 comes from ‘block_size’ being measured in bytes and not in bits). The default value for this parameter should be block_size*8. Implementors are allowed to constrain ‘segment_size’ to be a multiple of 8 for simplicity, but they’re encouraged to support arbitrary values for generality. Secret-key encryption modules should define two variables: block_size An integer value; the size of the blocks encrypted by this module, measured in bytes. For all feedback modes, the length of strings passed to the encrypt() and decrypt() must be a multiple of the block size. key_size An integer value; the size of the keys required by this module, measured in bytes. If key_size is None, then the algorithm accepts variable-length keys. This may mean the module accepts keys of any random length, or that there are a few different possible lengths, e.g. 16, 24, or 32 bytes. You cannot pass a key of length 0 (that is, the null string ‘’) as a variable-length key. Cipher objects should have two attributes: block_size An integer value equal to the size of the blocks encrypted by this object. For algorithms with a variable block size, this value is equal to the block size selected for this object. IV Contains the initial value which will be used to start a cipher feedback mode; it will always be a string exactly one block in length. After encrypting or decrypting a string, this value is updated to reflect the modified feedback text. It is read-only, and cannot be assigned a new value. Cipher objects require the following methods: decrypt(string) Decrypts ‘string’, using the key-dependent data in the object and with the appropriate feedback mode. The string’s length must be an exact multiple of the algorithm’s block size or, in CFB mode, of the segment size. Returns a string containing the plaintext. encrypt(string) Encrypts a non-empty string, using the key-dependent data in the object, and with the appropriate feedback mode. The string’s length must be an exact multiple of the algorithm’s block size or, in CFB mode, of the segment size. Returns a string containing the ciphertext. Here’s an example, using a module named ‘DES’: >>> import DES >>> obj = DES . new ( 'abcdefgh' , DES . MODE_ECB ) >>> plaintext = "Guido van Rossum is a space alien." >>> len ( plaintext ) 34 >>> obj . encrypt ( plaintext ) Traceback (innermost last): File "<stdin>" , line 1 , in ? ValueError : Strings for DES must be a multiple of 8 in length >>> ciphertext = obj . encrypt ( plain + 'XXXXXX' ) # Add padding >>> ciphertext '\021,\343Nq\214DY\337T\342pA\372\255\311s\210\363,\300j\330\250\312\347\342I\3215w\03561\303dgb/\006' >>> obj . decrypt ( ciphertext ) 'Guido van Rossum is a space alien.XXXXXX' References [ 1 ] NIST publication SP 800-38A, “Recommendation for Block Cipher Modes of Operation” ( http://csrc.nist.gov/encryption/modes/ ) [ 2 ] Applied Cryptography Changes 2002-04: Removed references to stream ciphers; retitled PEP; prefixed feedback mode constants with MODE_ ; removed PGP feedback mode; added CTR and OFB feedback modes; clarified where numbers are measured in bytes and where in bits. 2002-09: Clarified the discussion of key length by using “variable-length keys” instead of “arbitrary-length”. Acknowledgements Thanks to the readers of the python-crypto list for their comments on this PEP. Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-0272.rst Last modified: 2025-02-01 08:59:27 GMT Contents Abstract Introduction Specification References Changes Acknowledgements Copyright Page Source (GitHub) | 2026-01-13T08:49:04 |
https://www.python.org/download/alternatives#python-network | Alternative Python implementations | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Alternative Python implementations This site hosts the "traditional" implementation of Python (nicknamed CPython). A number of alternative implementations are available as well, namely PyPy (a fast implementation of Python with a JIT compiler) IronPython (Python running on .NET) MicroPython (Python running on microcontrollers and in the web browser ) Stackless Python (a branch of CPython supporting microthreads) Jython (Python running on the Java Virtual Machine) GraalPy (embeddable Python runtime for Java) Other parties have repackaged CPython. These re-packagings often include more libraries or are specialized for a particular application: Anaconda Python (a full Python distribution for data management, analysis and visualization of large data sets) ActiveState ActivePython (commercial and community versions, including scientific computing modules) Nuitka (a compiler that packages user code with CPython into a static binary for improved performance and IP protection) pyodide (a Python distribution for the browser and Node.js based on WebAssembly) WinPython (a portable scientific Python distribution for Windows) Python(x, y) (Scientific-oriented distribution based on Qt and Spyder) Conceptive Python SDK (targets business, desktop and database applications) PyIMSL Studio (a commercial distribution for numerical analysis – free for non-commercial use) eGenix PyRun (a portable Python runtime, complete with stdlib, frozen into a single 3.5MB - 13MB executable file) If you want to host and run Python in the cloud, these implementations may be right for you: PythonAnywhere (freemium hosted Python installation which lets you run Python in the browser, e.g. for tutorials, showcases) The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://docs.python.org/3/license.html#test-epoll | 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:49:04 |
https://core.forem.com/t/help#main-content | Help! - Forem Core Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Core Close Help! Follow Hide A place to ask questions and provide answers. We're here to work things out together. Create Post submission guidelines This tag is to be used when you need to ask for help , not to share an article you think is helpful . Please review our community guidelines When asking for help, please follow these rules: Title: Write a clear, concise, title Body: What is your question/issue (provide as much detail as possible)? What technologies are you using? What were you expecting to happen? What is actually happening? What have you already tried/thought about? What errors are you getting? Please try to avoid very broad "How do I make x" questions, unless you have used Google and there are no tutorials on the subject. about #help This is a place to ask for help for specific problems. Before posting, please consider the following: If you're asking for peoples opinions on a specific technology/metholody - #discuss is more appropriate. Are you looking for how to build x? Have you Googled to see if there is already a comprehensive tutorial available? Older #help posts 1 2 3 4 5 6 7 8 9 … 75 … 158 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem Core — Discussing the core forem open source software project — features, bugs, performance, self-hosting. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem Core © 2016 - 2026. Community building community Log in Create account | 2026-01-13T08:49:04 |
https://www.python.org/community/awards#python-network | Python Community Awards | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> News & Community >>> Community Awards Python Community Awards Python Software Foundation Community Service Awards are given to members of the community who significantly improve the Foundation's fulfillment of its mission. Python Software Foundation Distinguished Service Awards are given to members of the community whose long-term efforts have significantly influenced and shaped the Python community. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:04 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Frsionnach%2Fshift-left-reliability-4poo&title=Shift-Left%20Reliability&summary=We%27ve%20become%20exceptionally%20good%20at%20incident%20response.%20Modern%20teams%20restore%20service%20quickly%2C%20run...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:04 |
https://dev.to/geovane_oliveira | Geovane Oliveira - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Geovane Oliveira 404 bio not found Joined Joined on Dec 16, 2025 More info about @geovane_oliveira Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 2 posts published Comment 0 comments written Tag 0 tags followed Protecting an EC2 hosted web application with AWS WAF in practice Geovane Oliveira Geovane Oliveira Geovane Oliveira Follow Jan 8 Protecting an EC2 hosted web application with AWS WAF in practice # architecture # aws # devops # security Comments Add Comment 12 min read Securing Serverless APIs with Amazon Cognito and API Gateway JWT Authorizers Geovane Oliveira Geovane Oliveira Geovane Oliveira Follow Dec 24 '25 Securing Serverless APIs with Amazon Cognito and API Gateway JWT Authorizers # aws # security # serverless # awscommunitybuilder Comments Add Comment 5 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/t/programming/page/72 | Programming Page 72 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 69 70 71 72 73 74 75 76 77 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Roman Numerals in Go: The Self‑Correcting One‑Pass Trick Archdemon Archdemon Archdemon Follow Dec 17 '25 Roman Numerals in Go: The Self‑Correcting One‑Pass Trick # programming # algorithms # go # learning Comments Add Comment 4 min read Basics (Getting Started) with WJb Oleksandr Viktor Oleksandr Viktor Oleksandr Viktor Follow Dec 17 '25 Basics (Getting Started) with WJb # programming # webdev # ai Comments Add Comment 1 min read CRISPR Off-Target Prediction Was Never a Biology Problem Omnis Coder Omnis Coder Omnis Coder Follow Dec 17 '25 CRISPR Off-Target Prediction Was Never a Biology Problem # crispr # bioinformatics # genomics # programming 1 reaction Comments 1 comment 3 min read Start, Stop, and Continue for 2026 Aaron McCollum Aaron McCollum Aaron McCollum Follow Dec 19 '25 Start, Stop, and Continue for 2026 # webdev # programming # learning Comments Add Comment 3 min read Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 8 Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 # go # linux # opensource # programming 5 reactions Comments Add Comment 5 min read I Slashed My AI Coding Bills by 65% With This One Weird Trick. Vishal VeeraReddy Vishal VeeraReddy Vishal VeeraReddy Follow Dec 31 '25 I Slashed My AI Coding Bills by 65% With This One Weird Trick. # ai # programming # opensource # openai Comments Add Comment 5 min read Amazon S3 Explained: Simple Storage in the Cloud MATHAN S MATHAN S MATHAN S Follow Dec 18 '25 Amazon S3 Explained: Simple Storage in the Cloud # cloud # devops # aws # programming Comments Add Comment 1 min read MURAL: A Visual Collaboration Tool in the DevSecOps Periodic Table MATHAN S MATHAN S MATHAN S Follow Dec 18 '25 MURAL: A Visual Collaboration Tool in the DevSecOps Periodic Table # devops # mural # programming # opensource Comments Add Comment 1 min read Leetcode 39 Combination Sum Wincy H Wincy H Wincy H Follow Dec 17 '25 Leetcode 39 Combination Sum # leetcode # programming # python # tutorial Comments Add Comment 3 min read Torrance Motors: Building a Fast, Reliable Automotive Website with C++ — Challenges Faced and Future Goals Alfie John Alfie John Alfie John Follow Dec 18 '25 Torrance Motors: Building a Fast, Reliable Automotive Website with C++ — Challenges Faced and Future Goals # webdev # programming # ai # javascript Comments Add Comment 9 min read A Better Way to Run Git Worktrees Finally! Julio Daniel Reyes Julio Daniel Reyes Julio Daniel Reyes Follow Dec 16 '25 A Better Way to Run Git Worktrees Finally! # git # vibecoding # programming # ai 27 reactions Comments Add Comment 1 min read How We Actually Ship Complex Systems with AI Agents Ali Baqbani Ali Baqbani Ali Baqbani Follow Dec 18 '25 How We Actually Ship Complex Systems with AI Agents # ai # programming # softwaredevelopment # architecture Comments Add Comment 3 min read Productionizing Model Context Protocol Servers OnlineProxy OnlineProxy OnlineProxy Follow Dec 17 '25 Productionizing Model Context Protocol Servers # programming # ai # beginners # tutorial Comments Add Comment 7 min read 🚀 Launching Vyoma Labs: A Research-First Space for Building the Future of the Web Prasoon Jadon Prasoon Jadon Prasoon Jadon Follow Dec 17 '25 🚀 Launching Vyoma Labs: A Research-First Space for Building the Future of the Web # webdev # programming # startup # opensource Comments Add Comment 3 min read Vibe Coding hit a wall: How I fixed $0.30/error OOMs and cut AI costs by 70% renming wang renming wang renming wang Follow Dec 17 '25 Vibe Coding hit a wall: How I fixed $0.30/error OOMs and cut AI costs by 70% # webdev # ai # programming # productivity 1 reaction Comments 1 comment 2 min read Introducing temporal-contract: Type-Safe Temporal. io Workflows for TypeScript Benoit Travers Benoit Travers Benoit Travers Follow Dec 21 '25 Introducing temporal-contract: Type-Safe Temporal. io Workflows for TypeScript # typescript # node # programming # productivity 2 reactions Comments Add Comment 8 min read AWS CodeDeploy: A Beginner-Friendly Guide to Automated Deployments Ege Pakten Ege Pakten Ege Pakten Follow Dec 17 '25 AWS CodeDeploy: A Beginner-Friendly Guide to Automated Deployments # aws # codedeploy # programming # infrastructureascode Comments Add Comment 5 min read Atlassian Bamboo in the DevSecOps Periodic Table ABITHA N 24CB001 ABITHA N 24CB001 ABITHA N 24CB001 Follow Dec 18 '25 Atlassian Bamboo in the DevSecOps Periodic Table # devops # devsecops # programming # learning Comments Add Comment 1 min read StableJSON: A Practical Workspace for Serious JSON Work Debjit Dey Debjit Dey Debjit Dey Follow Dec 31 '25 StableJSON: A Practical Workspace for Serious JSON Work # programming # webdev # devtool # json Comments 1 comment 2 min read The New Field Keyword Improves Properties in C# 14 Adrián Bailador Adrián Bailador Adrián Bailador Follow Dec 17 '25 The New Field Keyword Improves Properties in C# 14 # csharp # dotnet # programming # webdev Comments Add Comment 6 min read I Built a Clean Age Calculator Because Most of Them Get the Details Wrong Momin Ali Momin Ali Momin Ali Follow Dec 18 '25 I Built a Clean Age Calculator Because Most of Them Get the Details Wrong # programming # webdev # javascript 1 reaction Comments 1 comment 2 min read AI-Powered Programming: Creating My Own Magical Flashcards Study App Daniel Daniel Daniel Follow for Datalaria Jan 10 AI-Powered Programming: Creating My Own Magical Flashcards Study App # showdev # ai # programming 5 reactions Comments 2 comments 5 min read Beyond the Screen: Why LLMs Don't Need Browsers (And Why We Think They Do) Edward Burton Edward Burton Edward Burton Follow Dec 17 '25 Beyond the Screen: Why LLMs Don't Need Browsers (And Why We Think They Do) # webdev # programming # ai # browser 1 reaction Comments Add Comment 8 min read YAML Formatter Pineapple Pineapple Pineapple Follow Dec 22 '25 YAML Formatter # webdev # programming # beginners # kubernetes Comments Add Comment 2 min read Day 73: Python Longest Palindromic Substring – Expand-Around-Center O(n^2) Technique for Max Palindrome (LeetCode #5 Guide) Shahrouz Nikseresht Shahrouz Nikseresht Shahrouz Nikseresht Follow Dec 23 '25 Day 73: Python Longest Palindromic Substring – Expand-Around-Center O(n^2) Technique for Max Palindrome (LeetCode #5 Guide) # challenge # python # algorithms # programming Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Fneisha1618%2Fcallbacks-vs-promises-4mi1 | Facebook에 로그인 Notice 계속하려면 로그인해주세요. Facebook에 로그인 계속하려면 로그인해주세요. 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:04 |
https://dev.to/t/kotlin/page/6 | Kotlin Page 6 - 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 Kotlin Follow Hide a cross-platform, statically typed, general-purpose programming language with type inference Create Post Older #kotlin posts 3 4 5 6 7 8 9 10 11 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The Subtle Art of Making Android Animations Feel Expensive Joseph Sanjaya Joseph Sanjaya Joseph Sanjaya Follow Oct 30 '25 The Subtle Art of Making Android Animations Feel Expensive # android # androiddev # mobile # kotlin 2 reactions Comments 1 comment 8 min read Wednesday Links - Edition 2025-10-29 Chris Kocel Chris Kocel Chris Kocel Follow Oct 29 '25 Wednesday Links - Edition 2025-10-29 # java # jvm # gradle # kotlin Comments Add Comment 1 min read Building Mutualockss: How I Created a Shared Digital Security App from Scratch | Sayanth V Sivadas Sayanth V Sivadas Sayanth V Sivadas Sayanth V Sivadas Follow Oct 27 '25 Building Mutualockss: How I Created a Shared Digital Security App from Scratch | Sayanth V Sivadas # programming # android # kotlin # beginners Comments Add Comment 4 min read Debugging Recompositions in Jetpack Compose Mohit Rajput Mohit Rajput Mohit Rajput Follow Oct 28 '25 Debugging Recompositions in Jetpack Compose # android # jetpackcompose # kotlin # recomposition 1 reaction Comments Add Comment 1 min read MapStruct: When a Helper Method Maps More Than You Asked For Petr Filaretov Petr Filaretov Petr Filaretov Follow Oct 28 '25 MapStruct: When a Helper Method Maps More Than You Asked For # java # kotlin # mapstruct 2 reactions Comments Add Comment 3 min read Chapter 3 - Methods Common to All Objects (Items 10-14) Rajani K Rajani K Rajani K Follow Sep 24 '25 Chapter 3 - Methods Common to All Objects (Items 10-14) # programming # java # kotlin # effectivejava Comments Add Comment 7 min read Compose Beginner 1: Why Jetpack Compose Changed Android Forever Abizer Abizer Abizer Follow Oct 27 '25 Compose Beginner 1: Why Jetpack Compose Changed Android Forever # android # kotlin # mobile # androiddev Comments Add Comment 3 min read How to Create an IoT App in Kotlin Multiplatform Karol Wrótniak Karol Wrótniak Karol Wrótniak Follow Oct 5 '25 How to Create an IoT App in Kotlin Multiplatform # kotlin # android # ios # iot Comments Add Comment 12 min read Master Jetpack Compose Animations — Bite‑Sized Guides to Make Your UI Pop ✨ Manoj Pedvi Manoj Pedvi Manoj Pedvi Follow Sep 26 '25 Master Jetpack Compose Animations — Bite‑Sized Guides to Make Your UI Pop ✨ # android # androiddev # jetpack # kotlin 1 reaction Comments Add Comment 2 min read Message Mirror: a tiny, resilient Android notification + SMS forwarder (Flutter + Kotlin) Arian Amiramjadi Arian Amiramjadi Arian Amiramjadi Follow Sep 21 '25 Message Mirror: a tiny, resilient Android notification + SMS forwarder (Flutter + Kotlin) # flutter # kotlin # notifications # android Comments Add Comment 7 min read looking for contributors for an open-source KMP project to automate office processes Matthew Avgul Matthew Avgul Matthew Avgul Follow Sep 20 '25 looking for contributors for an open-source KMP project to automate office processes # kotlin # kmp # jetbrains # automation 1 reaction Comments Add Comment 1 min read EasyLog - Intelligent Object Debugging Michael.I Michael.I Michael.I Follow Sep 19 '25 EasyLog - Intelligent Object Debugging # android # mobile # kotlin Comments Add Comment 3 min read This isn't Kotlin. This is Java, with `apply` syntax in JPlus. Goodbye, boilerplate. JPlus JPlus JPlus Follow Oct 22 '25 This isn't Kotlin. This is Java, with `apply` syntax in JPlus. Goodbye, boilerplate. # programming # tooling # kotlin # java Comments Add Comment 2 min read DataStore in Android: The Future of Local Key-Value Storage Vrushali Vrushali Vrushali Follow Sep 18 '25 DataStore in Android: The Future of Local Key-Value Storage # android # kotlin # datastore # jetpack Comments Add Comment 1 min read Why Every Android Dev Should Master Arrays Before Anything Else Vrushali Vrushali Vrushali Follow Sep 18 '25 Why Every Android Dev Should Master Arrays Before Anything Else # dsa # kotlin # android # mobile Comments Add Comment 1 min read JPlus – A Java Superset with Null Safety and Boilerplate Elimination JPlus JPlus JPlus Follow Oct 22 '25 JPlus – A Java Superset with Null Safety and Boilerplate Elimination # java # kotlin # tooling Comments Add Comment 2 min read Event Handling: Keep It Fast and Simple Maksim Matlakhov Maksim Matlakhov Maksim Matlakhov Follow Sep 30 '25 Event Handling: Keep It Fast and Simple # eventdriven # architecture # kotlin # backend 3 reactions Comments Add Comment 5 min read Building a Real-Time Heart Rate Monitoring App with Kotlin + Google Cloud Qandil Tariq Qandil Tariq Qandil Tariq Follow Sep 17 '25 Building a Real-Time Heart Rate Monitoring App with Kotlin + Google Cloud # android # googlecloud # kotlin # ai Comments Add Comment 2 min read Kotlin Efficiency: Code Smarter, Not Harder - Typealias 4wl2d 4wl2d 4wl2d Follow Oct 17 '25 Kotlin Efficiency: Code Smarter, Not Harder - Typealias # programming # mobile # android # kotlin 12 reactions Comments 4 comments 7 min read Model Context Protocol (MCP) Saidur Rahman Saidur Rahman Saidur Rahman Follow Oct 19 '25 Model Context Protocol (MCP) # ai # rag # kotlin # llm Comments Add Comment 1 min read Automatic resource cleanup in Jetpack ViewModels using AutoCloseable RockAndNull RockAndNull RockAndNull Follow Oct 7 '25 Automatic resource cleanup in Jetpack ViewModels using AutoCloseable # android # jetpackcompose # kotlin Comments 1 comment 2 min read From Callback Hell to Coroutines: An Evolutionary History of Android Concurrency Kavearhasi Viswanathan Kavearhasi Viswanathan Kavearhasi Viswanathan Follow Oct 4 '25 From Callback Hell to Coroutines: An Evolutionary History of Android Concurrency # androiddev # kotlin # architecture Comments Add Comment 5 min read SmartCV: An AI-Powered Resume Analyzer with Jetpack Compose & Kotlin Multiplatform Qandil Tariq Qandil Tariq Qandil Tariq Follow Sep 13 '25 SmartCV: An AI-Powered Resume Analyzer with Jetpack Compose & Kotlin Multiplatform # android # ai # kmp # kotlin Comments Add Comment 2 min read Kotlin Coroutines Cheat Sheet Bruno Pivoto Azevedo Bruno Pivoto Azevedo Bruno Pivoto Azevedo Follow Oct 15 '25 Kotlin Coroutines Cheat Sheet # kotlin # programming # coroutines # android 9 reactions Comments Add Comment 2 min read Wednesday Links - Edition 2025-10-15 Chris Kocel Chris Kocel Chris Kocel Follow Oct 15 '25 Wednesday Links - Edition 2025-10-15 # java # jvm # mongodb # kotlin 1 reaction Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://mac.getutm.app/ | UTM | Virtual machines for Mac ☰ Gallery Support Changes Download Securely run operating systems on your Mac Download Mac App Store Windows. Linux. Meet Apple Silicon . UTM employs Apple's Hypervisor virtualization framework to run ARM64 operating systems on Apple Silicon at near native speeds. On Intel Macs, x86/x64 operating system can be virtualized. In addition, lower performance emulation is available to run x86/x64 on Apple Silicon as well as ARM64 on Intel. For developers and enthusiasts, there are dozens of other emulated processors as well including: ARM32, MIPS, PPC, and RISC-V. Your Mac can now truly run anything. Emulate classic operating systems. Not only can you run the latest and greatest operating systems, you can also emulate older operating systems whether it's on PowerPC, SPARC, or x86_64. Check out the gallery for some examples of what you can run. Virtualize macOS as well. Run multiple instances of macOS on your Apple Silicon Mac with UTM. This can be useful for developers as well as security conscious users. Note that macOS VM support is limited to ARM based Macs running macOS Monterey or higher. Designed for macOS Unlike other free virtualization software, UTM was created for macOS and only for Apple platforms. It is designed completely from the ground up for the new style introduced in Big Sur. UTM looks and feels like a Mac app with all the privacy and security features you expect as well. QEMU and Apple Virtualization without the headache UTM uses QEMU , a decades old, free and open source emulation software that is widely used and actively maintained. While QEMU is powerful, it can be difficult to set up and configure with its plethora of command line options and flags. UTM is designed to give users the flexibility of QEMU without the steep learning curve that comes with it. UTM can also be configured to use Apple Virtualization , a native framework for virtualizing macOS and Linux on Apple Silicon. What's the difference in the Mac App Store version? UTM is and always will be completely free and open source. The Mac App Store version is identical to the free version and there are no features left out of the free version. The only advantage of the Mac App Store version is that you can get automatic updates. Purchasing the App Store version directly funds the development of UTM and shows your support . How do I contribute? You can find UTM on GitHub . You can also contribute to the QEMU project . Can I run games? No, probably not. UTM does not currently support GPU emulation/virtualization on Windows and therefore lacks support for 3D acceleration (e.g. OpenGL and DirectX). You may be able to run older games with software rendering options, but nothing with hardware acceleration. There is experimental support for hardware OpenGL acceleration on Linux through Virgl . UTM for iOS ? More Information Gallery Support Changes Guide Licenses Privacy Twitter GitHub Discord YouTube © 2025 osy • Template by CloudCannon | 2026-01-13T08:49:04 |
https://dev.to/about#main-content | About DEV - 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 About DEV DEV is a community of software developers getting together to help one another out. The software industry relies on collaboration and networked learning. We provide a place for that to happen. DEV is built on Forem : open source software designed to empower communities. Because our application is open source , you can inspect every little detail of the code, or chip in yourself! Forem is available for anyone interested in creating similar communities in any niche or passion. Visit our meta Forem, forem.dev for more information. We believe in transparency and adding value to the ecosystem. We hope you enjoy poking around and participating! Leadership DEV is led by Forem's co-founders Ben Halpern , Jess Lee , and Peter Frank ("PB&J"). Happy coding ❤️ 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://mail.python.org/mailman/listinfo/jobs | Mailman 3 Info | jobs@python.org - python.org Toggle navigation Postorius Sign In Sign Up Lists Archives Sign In Sign Up Jobs jobs@python.org Summary Python Job Board List PLEASE NOTE - IT IS NOT NECESSARY TO SUBSCRIBE TO THIS LIST IF YOU'RE A JOB SEEKER - ALL CURRENT JOBS ARE LISTED AT https://www.python.org/jobs/ This is the Python Job Board list, used internally by the Job Board Team. To contact the list owners, use the following email address: jobs-owner@python.org You have to sign in to visit the archives of this list. Subscription / Unsubscription To subscribe or unsubscribe from this list, please sign in first. If you have not previously signed in, you may need to set up an account with the appropriate email address. Sign In Postorius Documentation • GNU Mailman • Postorius Version 1.3.13 | 2026-01-13T08:49:04 |
https://dev.to/trusted-member#the-power-of-emoji-reactions | DEV Trusted Member Guide - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close DEV Trusted Member Guide With a community of over one million members on DEV, we could use a hand! We would greatly appreciate your help in enforcing our Code of Conduct and assisting new community members by kindly welcoming them & guiding them through site mechanics. Trusted Member Actions Clickable Demo Table of Contents What is a Trusted Member? How to Use Your Trusted Member Actions Becoming a Trusted Member What is a Trusted Member? Trusted Members are individuals who have been granted basic moderation abilities to assist us by moderating discussions, reporting problematic content, and fostering positive interactions among members. We select individuals for this role who we believe will be kind, friendly, inclusive, and help to uphold our Code of Conduct. As a Trusted Member, you will gain special abilities that allow you to do the following, which will affect the visibility of posts in our ranking algorithm and grant more exposure to higher quality articles in the search feed: Rank content 👍 👎 with emoji reactions Use the Flag to Admins icon 🧐 to report problematic content Access templated comments and post them as our mascot, Sloan the Official DEV Moderator . Note: We would like to emphasize that this role is meant to aid us in promoting friendly interactions and nurturing a healthy, inclusive, and supportive community. It is not meant to establish a hierarchy among members. We value and appreciate all DEV members and strive to ensure a safe, productive, and enjoyable experience for everyone! The creation of this role is intended to assist us in achieving these goals. How to Use Your Trusted Member Actions The Mod Panel Many of the Trusted Member actions are accessible from the Mod Panel. Trusted Members will see a shield icon on the left-hand side of a post page. Click on the shield and the Moderate Post panel will open on the right side of the page. From this panel, Trusted Users can take various actions. Rank Content with Emoji Reactions The Thumbs Up emoji helps boost content in our content ranking algorithm so that the post is granted more visibility within the search results and feed. Use the Thumbs Up 👍 for high-quality content that embodies the values and spirit of the DEV Community. The Thumbs Down emoji deprioritizes content so that it's less likely to be seen on the site. Use the Thumbs Down 👎 for posts that are factually incorrect, poorly written, and those which advertise products or services using stealthy or dishonest marketing tactics, and /or link to external content (e.g. "read more here”). If you notice content that violates our Code of Code of Conduct or Terms , please flag it using the Flag to Admins action so that our DEV team can take appropriate measures. For articles that are clearly spam, plagiarized, or offensive in nature, we recommend using the 🧐 reaction to flag them. Rate the Experience Level of a Post Trusted Members can rate posts’ experience levels on a 1-5 scale, using their best judgment, knowledge of the topic, and considering their own bias. The aim is to deliver more relevant content to each user’s feed based on their chosen experience level. To rate a post, open the Mod Panel, click Set experience level, and choose the option that best fits. Don’t worry about making a mistake or getting it exactly right. The rating is an average of multiple selections from different Trusted Members. Flag a User You have the option to flag a problematic user’s account from the Mod Panel by clicking "Moderating actions" then “Flag user.” This will flag all of their content for the admin to review. Use this action for spammy accounts only. For other issues like plagiarism or abusive behavior, please report them via our Report abuse page so that you can provide more context. Becoming a Trusted Member At DEV, we often grant the Trusted Member role to individuals who are particularly friendly and helpful in our community. We look for kind, inclusive, and empathetic individuals who genuinely enjoy assisting others. There are various ways this role is granted: Immediate Recognition: When we notice someone being a kind DEV citizen, we may grant them the Trusted Member role right away. Helpful Reports: If someone consistently sends in helpful reports, we may recognize their contributions and grant them the Trusted Member role. Request Consideration: Community members can reach out to us via support@dev.to , expressing their interest in becoming a Trusted Member. We evaluate their participation on DEV to determine their suitability. Note: We avoid granting this role to individuals who have violated our Code of Conduct or have not actively engaged enough in the community for us to assess their character. We also generally avoid selecting individuals who frequently share controversial posts or exhibit harsh and impatient behavior toward others. Expectations of a Trusted Member The Trusted Member role is granted to individuals we consider to be trustworthy and exemplary citizens of DEV. There are no strict expectations or requirements for involvement, meaning: No Time Quotas: There are no mandatory participation hours or time commitments. If you need to take a break due to personal reasons or decide that the role isn't for you, just let us know, and we can remove it from your DEV account. Inclusive Participation: We encourage individuals from all backgrounds to participate. While much of our content is in English, we welcome DEV members to write in the language of their choice. We have a diverse international community with sub-communities focused on different languages and cultures, such as #braziliandevs. Kindness and Empathy: The primary expectation of Trusted Members is to demonstrate kindness and empathy. They are required to adhere to our Code of Conduct and Terms and help ensure others on the site do the same. However, we strive to avoid gatekeeping, impatience, or frustration among Trusted Members. Handling challenging situations and individuals can be demanding, and it's important to represent DEV's empathetic values. In difficult moments, we recommend that Trusted Members involve the core DEV Team and refrain from engaging directly. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://neonstatus.com/ | Neon Status SUBSCRIBE SUBSCRIBE All Systems Operational Updated a few seconds ago Updated a few seconds ago Database Connectivity AWS ap-southeast-1 AWS ap-southeast-2 AWS eu-central-1 AWS eu-west-2 AWS sa-east-1 AWS us-east-1 AWS us-east-2 AWS us-west-2 Azure germanywestcentral Azure eastus2 Azure westus3 Operational Project/Branch Operations AWS ap-southeast-1 AWS ap-southeast-2 AWS eu-central-1 AWS eu-west-2 AWS sa-east-1 AWS us-east-1 AWS us-east-2 AWS us-west-2 Azure germanywestcentral Azure eastus2 Azure westus3 Operational Console API Global AWS ap-southeast-1 AWS ap-southeast-2 AWS eu-central-1 AWS eu-west-2 AWS sa-east-1 AWS us-east-1 AWS us-east-2 AWS us-west-2 Azure germanywestcentral Azure eastus2 Azure westus3 Operational Console Frontend Global AWS ap-southeast-1 AWS ap-southeast-2 AWS eu-central-1 AWS eu-west-2 AWS sa-east-1 AWS us-east-1 AWS us-east-2 AWS us-west-2 Azure germanywestcentral Azure eastus2 Azure westus3 Operational Account Creation Global AWS ap-southeast-1 AWS ap-southeast-2 AWS eu-central-1 AWS eu-west-2 AWS sa-east-1 AWS us-east-1 AWS us-east-2 AWS us-west-2 Azure germanywestcentral Azure eastus2 Azure westus3 Operational Console Login Global AWS ap-southeast-1 AWS ap-southeast-2 AWS eu-central-1 AWS eu-west-2 AWS sa-east-1 AWS us-east-1 AWS us-east-2 AWS us-west-2 Azure germanywestcentral Azure eastus2 Azure westus3 Operational Website Global Operational Status page for neon.com History (Last 30 days) High connection latency in US-East-1 Cell-1 Degraded Performance Incident Status Degraded Performance Components Database Connectivity Locations AWS us-east-1 January 7, 2026 3:17PM UTC INVESTIGATING Starting at approximately 13:55 UTC January 07, 2026, customers may experience failures or delays in database connectivity. We are actively investigating the issue. Further updates will be provided within the next hour, or as events warrant. January 7, 2026 4:05PM UTC MONITORING Between 13:55 UTC and 15:45 UTC January 07, 2026, customers may have experienced failures or delays in database connectivity. The issue has been mitigated. We will continue to monitor the platform and will provide a final update in 1 hour. January 7, 2026 4:31PM UTC RESOLVED Between 13:55 UTC and 15:45 UTC January 07, 2026, customers may have experienced failures or delays in database connectivity. The issue has been fully resolved. All affected components are operating normally again. Status History Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription | 2026-01-13T08:49:04 |
https://dev.to/djuleayo/service-as-architecture-reversal-2gli#comments | Service as Architecture Reversal - 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 djuleayo Posted on Jan 12 • Originally published at e3690c49.personalpage-ahl.pages.dev on Jan 12 Service as Architecture Reversal # architecture # discuss # webdev Service as Architecture Reversal Link to heading In the early internet, the intent was simple: distribute textual files with minimal markup. To support this, a client–server architecture was adopted. The naming was not accidental. A server served . The client was the master . The server could not act unless requested. It could not speak unless spoken to. This asymmetry was a core design principle of the internet. Today, our intuition feels inverted. We scroll. We are notified. We are fed. It feels as if we are no longer the masters of the system, but its dependents. How did this reversal happen? Capability Link to heading A service exposes a capability. Take a barber. A haircut is a convenience — until you cannot cut your own hair. At that point, convenience becomes dependency. The moment you lose capability, the service becomes a control surface . This is exactly what happened to software. Software as a Service is an architectural reversal : instead of software serving on request, access to capability itself is mediated. You no longer act directly. You must go through the service. Control Surfaces Link to heading Consider a simple example: taking a screenshot in WhatsApp. You own the hardware. The hardware is capable. The action is legal. You want to do it. Yet you cannot. The application forbids it. And who grants the application that authority? The operating system. This is the root. Modern operating systems increasingly allow applications to define rules over hardware you own. Capability is no longer assumed — it is granted. A second example is even more revealing: offline functionality . Your computer is powerful enough to edit documents, organize files, or process data locally. Yet many tools refuse to function without an internet connection. Not because computation is impossible — but because capability has been relocated behind a service boundary. When the network disappears, so does your ability to act. The Reversal Link to heading Most people will never modify an operating system. They will never build tools. They will accept the service. And so the architecture completes its reversal. The system that was meant to serve becomes a gatekeeper. The user that was meant to command becomes dependent. This is not a conspiracy. It is the cumulative result of convenience traded for capability. Resolution Link to heading The loss of freedom did not begin with surveillance or advertising. It began earlier — with the quiet removal of user capability. The way forward is not rejecting services. It is refusing to confuse convenience with ownership . Use services where they save time. Avoid them where they become gates. Prefer tools that work locally. Prefer systems that degrade gracefully. Prefer architectures where capability exists before permission. Because in the end, whoever holds capability holds agency. Freedom didn’t disappear when we were watched. It disappeared when we stopped being capable. 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 djuleayo Follow Building graph-first systems, dynamically constructed parsers. Into DX, and composable automation. I write about real system design problems — not trends Education BCS CS Work Lead Software Engineer Joined Jul 25, 2025 More from djuleayo You Should Not Outsource Your Topological Sort # algorithms # architecture # computerscience 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://dev.to/t/ebpf | Ebpf - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close # ebpf Follow Hide Create Post Older #ebpf posts 1 2 3 4 5 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu eBPF: Experiencing eBPF with Cilium kt kt kt Follow Jan 12 eBPF: Experiencing eBPF with Cilium # cilium # ebpf # kubernetes # network 1 reaction Comments Add Comment 8 min read eBPF Tutorial by Example: BPF Arena for Zero-Copy Shared Memory 云微 云微 云微 Follow Jan 6 eBPF Tutorial by Example: BPF Arena for Zero-Copy Shared Memory # ebpf # arena # memory Comments Add Comment 11 min read eBPF Tutorial: Tracing CUDA GPU Operations 云微 云微 云微 Follow Dec 30 '25 eBPF Tutorial: Tracing CUDA GPU Operations # ebpf # cuda # gpu Comments Add Comment 12 min read eBPF Tutorial: Transparent Text Replacement in File Reads 云微 云微 云微 Follow Dec 23 '25 eBPF Tutorial: Transparent Text Replacement in File Reads # ebpf # kernel # tracing Comments Add Comment 10 min read Linux Kernel Architecture: From Ring 0 to Network Stack & eBPF kt kt kt Follow Jan 10 Linux Kernel Architecture: From Ring 0 to Network Stack & eBPF # linux # kernel # ebpf # programming Comments Add Comment 9 min read eBPF Tutorial by Example 32: Wall Clock Profiling with Combined On-CPU and Off-CPU Analysis 云微 云微 云微 Follow Dec 16 '25 eBPF Tutorial by Example 32: Wall Clock Profiling with Combined On-CPU and Off-CPU Analysis # ebpf # profiler # tracing Comments Add Comment 13 min read eBPF Tutorial by Example: Tracing Intel NPU Kernel Driver Operations 云微 云微 云微 Follow Dec 9 '25 eBPF Tutorial by Example: Tracing Intel NPU Kernel Driver Operations # ebpf # npu # kernel Comments Add Comment 9 min read 10,000 eBPF Events to 1 Alert: Don’t burn the CPU Parth Shah Parth Shah Parth Shah Follow Dec 13 '25 10,000 eBPF Events to 1 Alert: Don’t burn the CPU # ebpf # linux # kubernetes 1 reaction Comments 2 comments 5 min read eBPF Tutorial: Introduction to the BPF Scheduler 云微 云微 云微 Follow Nov 25 '25 eBPF Tutorial: Introduction to the BPF Scheduler # ebpf # scheduler # kernel Comments Add Comment 9 min read PulseGuard: Real-time Heart Monitoring with eBPF & Cilium Sundus Hussain Sundus Hussain Sundus Hussain Follow Nov 22 '25 PulseGuard: Real-time Heart Monitoring with eBPF & Cilium # ebpf # cilium 5 reactions Comments Add Comment 4 min read Extending eBPF Beyond Its Limits: Custom kfuncs in Kernel Modules 云微 云微 云微 Follow Dec 2 '25 Extending eBPF Beyond Its Limits: Custom kfuncs in Kernel Modules # ebpf # kernel # kfunc 2 reactions Comments Add Comment 11 min read eBPF Tutorial by Example: Implementing the `scx_nest` Scheduler 云微 云微 云微 Follow Nov 18 '25 eBPF Tutorial by Example: Implementing the `scx_nest` Scheduler # ebpf # scheduler # kernel Comments Add Comment 17 min read eBPF Tutorial by Example: Building a High-Performance XDP Packet Generator 云微 云微 云微 Follow Nov 11 '25 eBPF Tutorial by Example: Building a High-Performance XDP Packet Generator # ebpf # xdp # network Comments Add Comment 9 min read eBPF Tutorial by Example: Monitoring GPU Driver Activity with Kernel Tracepoints 云微 云微 云微 Follow Nov 4 '25 eBPF Tutorial by Example: Monitoring GPU Driver Activity with Kernel Tracepoints # ebpf # gpu # kernel Comments Add Comment 13 min read eBPF Tutorial: Privilege Escalation via File Content Manipulation 云微 云微 云微 Follow Oct 28 '25 eBPF Tutorial: Privilege Escalation via File Content Manipulation # ebpf # security # lsm Comments Add Comment 7 min read Zero-Code Observability: Using eBPF to Auto-Instrument Services with OpenTelemetry Nabin Debnath Nabin Debnath Nabin Debnath Follow Nov 7 '25 Zero-Code Observability: Using eBPF to Auto-Instrument Services with OpenTelemetry # observability # ebpf # opentelemetry # devops 4 reactions Comments Add Comment 5 min read eBPF Observability and Continuous Profiling with Parca Fatih Koç Fatih Koç Fatih Koç Follow Oct 27 '25 eBPF Observability and Continuous Profiling with Parca # ebpf # parca # observability # devops 3 reactions Comments Add Comment 11 min read Improving Network Performance with Custom eBPF-based Schedulers Ian Chen Ian Chen Ian Chen Follow Oct 20 '25 Improving Network Performance with Custom eBPF-based Schedulers # scheduler # ebpf # cloudnative Comments Add Comment 12 min read XDP: The Ultra-Fast Firewall Inside Linux Joseph Ligier Joseph Ligier Joseph Ligier Follow Oct 16 '25 XDP: The Ultra-Fast Firewall Inside Linux # ebpf # aya # rust # networking Comments Add Comment 2 min read AgentSight: Keeping Your AI Agents Under Control with eBPF-Powered System Observability 云微 云微 云微 Follow Oct 6 '25 AgentSight: Keeping Your AI Agents Under Control with eBPF-Powered System Observability # ebpf # ai # observability Comments Add Comment 12 min read eBPF Tutorial: Energy Monitoring for Process-Level Power Analysis 云微 云微 云微 Follow Oct 14 '25 eBPF Tutorial: Energy Monitoring for Process-Level Power Analysis # ebpf # energy # monitoring 1 reaction Comments Add Comment 16 min read The GPU Observability Gap: Why We Need eBPF on GPUs 云微 云微 云微 Follow Oct 21 '25 The GPU Observability Gap: Why We Need eBPF on GPUs # ebpf # gpu # kernel 1 reaction Comments Add Comment 18 min read 04 – eBPF Uprobes: Tracing gRPC Headers by Unpacking Go Function Internals Mahesh Rayas Mahesh Rayas Mahesh Rayas Follow Aug 3 '25 04 – eBPF Uprobes: Tracing gRPC Headers by Unpacking Go Function Internals # ebpf # go # grpc # rust 1 reaction Comments Add Comment 10 min read # 03- Lets understand Kprobes & Kretprobes Mahesh Rayas Mahesh Rayas Mahesh Rayas Follow Jul 20 '25 # 03- Lets understand Kprobes & Kretprobes # ebpf # rust # linux # tracing Comments Add Comment 6 min read # 02 - Understanding eBPF Core Building Blocks Mahesh Rayas Mahesh Rayas Mahesh Rayas Follow Jul 13 '25 # 02 - Understanding eBPF Core Building Blocks # ebpf # programming # monitoring 1 reaction Comments Add Comment 6 min read loading... trending guides/resources eBPF Tutorial by Example: Building a High-Performance XDP Packet Generator Zero-Code Observability: Using eBPF to Auto-Instrument Services with OpenTelemetry eBPF Tutorial by Example 32: Wall Clock Profiling with Combined On-CPU and Off-CPU Analysis Extending eBPF Beyond Its Limits: Custom kfuncs in Kernel Modules eBPF Tutorial by Example: Monitoring GPU Driver Activity with Kernel Tracepoints eBPF Tutorial by Example: Tracing Intel NPU Kernel Driver Operations PulseGuard: Real-time Heart Monitoring with eBPF & Cilium eBPF Tutorial: Transparent Text Replacement in File Reads eBPF Tutorial: Introduction to the BPF Scheduler 10,000 eBPF Events to 1 Alert: Don’t burn the CPU Linux Kernel Architecture: From Ring 0 to Network Stack & eBPF eBPF Tutorial: Tracing CUDA GPU Operations eBPF Tutorial by Example: Implementing the `scx_nest` Scheduler eBPF: Experiencing eBPF with Cilium eBPF Tutorial by Example: BPF Arena for Zero-Copy Shared Memory 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://twitter.com/EdWantuil | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:04 |
https://docs.python.org/3/license.html#openssl | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:49:04 |
https://dev.to/arsalanmeee/azure-introduces-new-networking-updates-for-better-security-and-reliability-5682#comments | Azure Introduces New Networking Updates for Better Security and Reliability - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Arsalan Mlaik for Arsalan Malik Posted on Dec 7, 2025 Azure Introduces New Networking Updates for Better Security and Reliability # azure # networking # news # career Published on Makemychance Microsoft Azure has rolled out new networking improvements aimed at helping developers build more secure, stable, and highly available cloud applications. The latest updates strengthen DDoS protection , improve traffic filtering , and offer deeper network monitoring , making it easier for developers and DevOps teams to identify issues faster. Azure’s upgraded load balancing and automatic failover features also reduce downtime during heavy traffic or service interruptions. For high-availability workloads, Azure now provides improved zone redundancy , smarter cross-region routing , and more efficient connection management. These changes support developers working on distributed systems, microservices, and global applications. For general information, users can check the Azure homepage ( https://azure.microsoft.com ) or Microsoft’s website ( https://www.microsoft.com ). 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 Arsalan Malik Follow Read More Makemychance More from Arsalan Malik Google Workspace Studio Agents: A Simple Guide for Developers # ai # cloud # network # news 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:04 |
https://gg.forem.com/ | Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close Welcome to Gamers Forem — part of the Forem network! We're a place where gamers unite, level up, and share epic adventures. Create account Log in Home About Contact Other Code of Conduct Privacy Policy Terms of Use Twitter Facebook Github Instagram Twitch Mastodon Popular Tags #gamedev #indie #pcgaming #steam #xbox #mmorpg #indiegames #gamepass #cloudgaming #nintendoswitch #blizzard #nintendo #moba #gamedeals #squareenix #retrogaming #ubisoft #mobilegaming #boardgames #vrgaming #esports #gaminghardware #rpg #fps #battleroyale #strategygames #gameaccessories #epicgames #speedrunning #rigs Gamers Forem An inclusive community for gaming enthusiasts Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. Posts Relevant Latest Top Forty Hours on Arrakis: A Dune Awakening Experience Evan Lausier Evan Lausier Evan Lausier Follow Jan 5 Forty Hours on Arrakis: A Dune Awakening Experience # steam # pcgaming # mmorpg # openworld Comments Add Comment 4 min read How AI World Models Are Changing Video Games Manu Manu Manu Follow Jan 3 How AI World Models Are Changing Video Games # discuss # career # gamedev 1 reaction Comments Add Comment 3 min read Sneak peek on a game im developing Gomes Gomes Gomes Follow Jan 8 Sneak peek on a game im developing # gamedev 6 reactions Comments 1 comment 1 min read My first game - Online Sudoku Corbin Corbin Corbin Follow Jan 2 My first game - Online Sudoku # gamedev # sudoku # puzzlegames # indie 4 reactions Comments Add Comment 1 min read Блогер нашёл способ воспроизводить на PS5 содержимое обычных компакт-дисков ad layer ad layer ad layer Follow Nov 27 '25 Блогер нашёл способ воспроизводить на PS5 содержимое обычных компакт-дисков # gaminghardware # modding # playstation Comments 1 comment 1 min read Managing PS2 BIOS Files Max Hunter Max Hunter Max Hunter Follow Dec 22 '25 Managing PS2 BIOS Files # ps2bios # bios # pcsx2 # aethersx2 5 reactions Comments Add Comment 1 min read Best Primer For Miniatures, The Confident Choice For Perfect Coverage Matthew Negus Matthew Negus Matthew Negus Follow Nov 20 '25 Best Primer For Miniatures, The Confident Choice For Perfect Coverage # boardgames # gameaccessories Comments Add Comment 5 min read 🍋 LemonLoader — Real-World Android Mod Loader for Unity Games Miller Miller Miller Follow Dec 19 '25 🍋 LemonLoader — Real-World Android Mod Loader for Unity Games # gamedev # modding # pcgaming # steam Comments 1 comment 2 min read 7 Hard Truths I Learned Running a Gaming Community for 13 Years Howard Howard Howard Follow Dec 9 '25 7 Hard Truths I Learned Running a Gaming Community for 13 Years # community # clans # pcgaming # advice 30 reactions Comments 3 comments 4 min read My First game - Comms Under Fire Shaquille Niekerk Shaquille Niekerk Shaquille Niekerk Follow Dec 11 '25 My First game - Comms Under Fire # gamedev # indie # cloudgaming # singleplayer 8 reactions Comments 3 comments 1 min read 🎮 *brkrs*: A Brand New Take on Classic Brick-Breaking – Play It, Tweak It, Own It! Christian Ledermann Christian Ledermann Christian Ledermann Follow Dec 7 '25 🎮 *brkrs*: A Brand New Take on Classic Brick-Breaking – Play It, Tweak It, Own It! # speckit # gamedev # bevy # arkanoid 12 reactions Comments 5 comments 4 min read 🚀 Launching Market Tycoon: A Casual Supermarket Management Game! seagames seagames seagames Follow Dec 6 '25 🚀 Launching Market Tycoon: A Casual Supermarket Management Game! # indie # gamedev # pcgaming # playstation 48 reactions Comments 1 comment 3 min read 💥 When Your Game Plays YOU: The Algorithm Behind Marvel Rivals Faisal Mujahid Faisal Mujahid Faisal Mujahid Follow Dec 9 '25 💥 When Your Game Plays YOU: The Algorithm Behind Marvel Rivals # gamedev # pcgaming # fps # battleroyale 2 reactions Comments 1 comment 1 min read 🚇 Metro — The Only Series That Made Me Afraid of Breathing Faisal Mujahid Faisal Mujahid Faisal Mujahid Follow Dec 3 '25 🚇 Metro — The Only Series That Made Me Afraid of Breathing # indie # pcgaming # gamedev # playstation 1 reaction Comments 2 comments 1 min read Path of Exile Economy Analysis: How Drop Rates, Crafting Probability, and Player Behavior Shape the Market Backend Admin Backend Admin Backend Admin Follow Nov 25 '25 Path of Exile Economy Analysis: How Drop Rates, Crafting Probability, and Player Behavior Shape the Market # gamedev # gameanalytics # dataanalysis # pathofexile 4 reactions Comments 2 comments 3 min read I Built a Free Spelling Bee Game You Can Play Right Now Vinish Kapoor Vinish Kapoor Vinish Kapoor Follow Nov 27 '25 I Built a Free Spelling Bee Game You Can Play Right Now # gamedev # ai 7 reactions Comments 3 comments 1 min read Will Activists using Fortnite to fight ICE Shift Debate? Jayant Harilela Jayant Harilela Jayant Harilela Follow Nov 23 '25 Will Activists using Fortnite to fight ICE Shift Debate? # fortnite # pitabreadface # defineamerican # robloxprotests 3 reactions Comments 2 comments 5 min read One Year of Building My Untitled Horror Inspired OS Game STG STG STG Follow Nov 19 '25 One Year of Building My Untitled Horror Inspired OS Game # indie # gamedev # pcgaming # modding 4 reactions Comments 10 comments 2 min read loading... #discuss Discussion threads targeting the whole community #watercooler Light, and off-topic conversation. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:49:04 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.