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.
...GitHub Usually when we reference an issue from bpo, we use bpo-XYZ but with Github, we will have a new reference with this format https://github.com/python/cpython/issue/XYZ. Because we will migrate the issues from bpo to GitHub, we need to have a new field on bpo for the reference to the issues on GitHub, and the same thing on Github for the 'eventual' reference from bpo. For GitHub, we need to add origin: https://bugs.python.org/issueXYZ. For bpo, add a new field moved to: https://github.com/p...
...github.com/python/bedevere) [4]the-knights-who-say-ni (https://github.com/python/the-knights-who-say-ni) [5]Getting permanent links to files (https://help.github.com/articles/getting-permanent-links-to-files/) [6]Closing issues using keywords (https://help.github.com/articles/closing-issues-using-keywords/) [7]About GitHub email notifications (https://help.github.com/articles/about-email-notifications/) [8]Unofficial GitHub mirror of Roundup (https://github.com/roundup-t...
...GitHub relies on GitHub continuing to allow API access. We are utilizing the GitHub Pull Request workflow, however all of those changes live inside of Git. So a mirror of the GitHub repositories can easily contain all of those Pull Requests. We would potentially lose any comments if GitHub suddenly turned "evil", but the changes themselves would still exist. We are utilizing the GitHub repository hosting feature, however since this is just git moving away from GitHub is as simple as pushing the ...
...GitHub issues) will have to be updated. Setting up a redirect for each migrated issue on bpo might mitigate the issue, however -- if references in migrated messages are not updated -- it will cause confusion (e.g. if bpo issue #1234 becomes GitHub issue #4321, a reference to #1234 in a migrated message could link to bpo #1234 and bpo can redirect to GitHub issue #4321, but new references to #1234 will link to GitHub PR #1234 rather than GitHub issue #4321). Manually having to specify a bpo- or g...
...GitHub account, which will be done through a new field in a user's profile. This does implicitly require that contributors will need both a GitHub [2] and bugs.python.org account in order to sign the CLA and contribute through GitHub. An API is provided to query bugs.python.org to see if a GitHub username corresponds to someone who has signed the CLA. Making a GET request to e.g. http://bugs.python.org/user?@template=clacheck&github_names=brettcannon,notanuser returns a JSON dictionary with ...
...GitHub, translations will be hosted on GitHub. For consistency and discoverability, all translations should be in the same GitHub organization and named according to a common pattern. Given that we want translations to be official, and that Python already has a GitHub organization, translations should be hosted as projects of the Python GitHub organization. For consistency, translation repositories should be called python-docs-LANGUAGE_TAG [22], using the language tag used in paths: without regi...
...GitHub Organization Purpose The Python Software Foundation exists to promote, protect, and advance the Python programming language, to fulfill that mission we have created a GitHub organization, @psf, to support and protect projects that have outgrown ownership by their original author. What is offered Repositories may be transferred to the @psf organization under the following criteria: The repository is relevant to the Python ecosystem at large and has broad interest among the community, or...
...GitHub and BitBucket to submit proposed changes using the standard pull request workflows offered by those tools SHOULD be open to customisation to meet the needs of CPython core development, including providing a potential path forward for the proposed migration to a core reviewer model in PEP 462 The preference for self-hosting without ongoing fees rules out the free-as-in-beer providers like GitHub and BitBucket, in addition to the various proprietary source code management offerings. The pr...
...GitHub [github]. Acknowledgements Armin Rigo essentially proposed this mechanism when presented with the idea of "module properties", and educated the author both on the complexities of the problem and the proper solution. Nathaniel J. Smith pointed out the 3.5 extension about assigning to __class__ on module objects, and provided the example. References [github] The branch is here: https://github.com/larryhastings/cpython/tree/module-properties A pull request against the main CPython rep...
...GitHub issue or GitHub pull request so that your changes don't get lost. When in doubt about where to send your changes, please check first with the PEP author and/or a PEP editor. PEP authors with write access to the PEP repository can update the PEPs themselves by using "git push" or the GitHub PR interface to submit their changes. Transferring PEP Ownership It occasionally becomes necessary to transfer ownership of PEPs to a new champion. In general, it is preferable to retain the original...
Version: None
Released: Dec. 8, 2023
This is the first maintenance release of Python 3.12 Python 3.12 is the newest major release of the Python programming language, and it contains many new features and optimizations. 3.12.1 is the latest maintenance release, containing more than 400 bugfixes, build improvements and documentation changes since 3.12.0. Major new features …
View Release Notes
Released: Feb. 6, 2024
This is the second maintenance release of Python 3.12 Python 3.12 is the newest major release of the Python programming language, and it contains many new features and optimizations. 3.12.2 is the latest maintenance release, containing more than 350 bugfixes, build improvements and documentation changes since 3.12.1. Major new features …
Released: April 9, 2024
This is the third maintenance release of Python 3.12 Python 3.12 is the newest major release of the Python programming language, and it contains many new features and optimizations. 3.12.3 is the latest maintenance release, containing more than 300 bugfixes, build improvements and documentation changes since 3.12.2. Major new features …
Location: Mountain View, California United States
Required Skills: Proficiency in writing optimized and clean Python code, with a strong understanding of Python libraries and frameworks like Flask and FastAPI with at least 5 years of experience Strong knowledge of PostgreSQL, including schema design, performance tuning, and advanced query optimization. Experience with other databases is a plus. …
...GitHub repository of Python 0.9.1 source.
Released: Sept. 17, 2020
This is the second release candidate of Python 3.9 This release, 3.9.0rc2, is the last preview before the final release of Python 3.9.0 on 2020-10-05. In the mean time, we strongly encourage maintainers of third-party Python projects to prepare their projects for 3.9 compatibility during this phase. As always, …
...GitHub repo [5]bpo-44123: Make function parameter sentinel values true singletons [6]The "sentinels" package on PyPI [7]The "sentinel" package on PyPI [8]Discussion thread about type signatures for these sentinels on the typing-sig mailing list Copyright This document is placed in the public domain or under the CC0-1.0-Universal license, whichever is more permissive. Source: https://github.com/python/peps/blob/master/pep-0661.rst
...GitHub issues and pull requests. Approving a pull request by any team member allows it to be merged without further process. All merged pull requests end up in the next stable version of Rust. Notifying relevant people by mentions is important. Listening to the firehose of e-mails for all GitHub activity is not popular. There are planning and triage meetings open to the public happening on IRC and Discord. They are not very popular because most of work happens through GitHub. Discussions als...
...github.com:python/cpython.git main # If it looks OK, take the plunge. There's no going back! $ git push --tags git@github.com:python/cpython.git main # For a **new branch** release, i.e. first beta: $ git push --dry-run --tags git@github.com:python/cpython.git X.Y $ git push --dry-run --tags git@github.com:python/cpython.git main # If it looks OK, take the plunge. There's no going back! $ git push --tags git@github.com:python/cpython.git X.Y $ git push --tags git@github.com:python/cpytho...
Location: Remote from Argentina, Argentina Argentina or rest of Latinamerica
Telecommuting: Yes
Python full stack advanced or intermediate Level of English Great opportunity and benefits Career dev English lessons Gym paid Salary in USD 3 weeks vacations Rental warranty covered Healthcare etc..