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.
...Git Wiki. Git Buch (German). Offline documentation Git has builtin help: run git help $TOPIC. For example, run git help git or git help help. Quick start Download and installation Unix users: download and install using your package manager. Microsoft Windows: download git-for-windows. MacOS X: use git installed with XCode or download from MacPorts or git-osx-installer or install git with Homebrew: brew install git. git-cola (repository) is a Git GUI written in Python and GPL licensed. Linu...
...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 ...
...Git. This may change commit ids, but after that, it should be easy to mirror the official Git branches and repositories far and wide. Where would the GitLab instance live? Physically, in whatever hosting provider GitLab chooses. We would point gitlab.python.org (or git.python.org?) to this host. References [1]Open Hub Statistics <https://www.openhub.net/repositories/compare> [2]Hg-Git mercurial plugin <https://hg-git.github.io/> [3]https://about.gitlab.com/ Cop...
...git The patches could be created with git diff master > stuff-i-did.patch, too, but git format-patch | git am knows some tricks (empty files, renames, etc) that ordinary patch can't handle. git grabs "Stuff I did" out of the commit message to create the file name 0001-Stuff-I-did.patch. See Patch Review below for a description of the git-format-patch format. # Get the mainline code. git clone git://code.python.org/python/trunk cd trunk # Edit some code. git commit -a -m 'Stuff I did.' # Crea...
...github.com/python/core-workflow/issues/7. Create https://git.python.org Just as hg.python.org [1] currently points to the Mercurial repository for Python, git.python.org should do the equivalent for the Git repository. Backup of pull request data Since GitHub [2] is going to be used for code hosting and code review, those two things need to be backed up. In the case of code hosting, the backup is implicit as all non-shallow Git [4] clones contain the full history of the repository, hence the...
...GitHub and BitBucket, in addition to the various proprietary source code management offerings. The preference for Mercurial support not only rules out GitHub, but also other Git-only solutions like GitLab and Gitorious. The hard requirement for online editing support rules out the Apache Allura/HgForge combination. The preference for a fully open source solution rules out RhodeCode. Of the various options considered by the author of this proposal, that leaves Kallithea SCM as the proposed founda...
...git+ssh://git@github.com/aio-libs/aiohttp.git@master aiohttp = { git = "ssh://git@github.com/aio-libs/aiohttp.git", revision = "master" } Environment Markers aiohttp >= 3.6.1; python_version >= '3.8' aiohttp = { version = ">= 3.6.1", markers = "python_version >= '3.8'" } A slightly extended example of the above, where a particular version of aiohttp is required based on the interpreter version. aiohttp >= 3.6.1; python_version >= '3.8' aiohttp >= 3.0.0, < 3.6.1;...
...Git Home page https://git-scm.com/ vcs command git vcs field git requested_revision field A tag name, branch name, Git ref, commit hash, shortened commit hash, or other commit-ish. commit_id field A commit hash (40 hexadecimal characters sha1). Note Installers can use the git show-ref and git symbolic-ref commands to determine if the requested_revision corresponds to a Git ref. In turn, a ref beginning with refs/tags/ corresponds to a tag, and a ref beginning with refs/remotes/origin/ afte...
...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/cpython.git main # For all other releases: $ git push --dry-run --tags git@github.com:python/cpython...
...git Gerrit uses git as the actual storage mechanism for patches, and automatically handles merging of approved patches. By contrast, Kallithea use the RhodeCode created vcs <https://pythonhosted.org/vcs/> library as an abstraction layer over specific DVCS implementations (with Mercurial and git backends currently available). Zuul is also directly integrated with git for patch manipulation - as far as I am aware, this part of the design currently isn't pluggable. However, at PyCon US 2014, ...
...Repository for PO Files Considering that each translation team may want to use different translation tools, and that those tools should easily be synchronized with git, all translations should expose their .po files via a git repository. Considering that each translation will be exposed via git repositories, and that Python has migrated to GitHub, translations will be hosted on GitHub. For consistency and discoverability, all translations should be in the same GitHub organization and named accor...
...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...
...git repository is available at [2]. References [1]https://mail.python.org/pipermail/python-ideas/2016-September/042141.html [2]https://github.com/1st1/cpython/tree/asyncomp [3]http://bugs.python.org/issue28008 Acknowledgments I thank Guido van Rossum, Victor Stinner and Elvis Pranskevichus for their feedback, code reviews, and discussions around this PEP. Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/master/pep-05...
...github.com/markrwilliams/manylinux/commit/e9493d55471d153089df3aafca8cfbcb50fa8093#diff-3eda4130bdba562657f3ec7c1b3f5720 [21]auditwheel manylinux2 branch (https://github.com/markrwilliams/auditwheel/tree/manylinux2) [22]pip manylinux2 branch https://github.com/markrwilliams/pip/commits/manylinux2 [23]Calendar Versioning http://calver.org/ Copyright This document has been placed into the public domain. Source: https://github.com/python/peps/blob/master/pep-0571.rst
...git repository. Recommendation for combined feature backports If a redistributor chooses to backport the environment variable based configuration setting from this PEP to a modified Python version that also implements the configuration file based PEP 476 backport, then the environment variable should take precedence over the system-wide configuration setting. This allows the setting to be changed for a given user or application, regardless of the installation-wide default behaviour. Example ...
...git repository is available at [1]. References [1]https://github.com/1st1/cpython/tree/async_gen [2]https://mail.python.org/pipermail/python-dev/2016-September/146267.html [3]http://bugs.python.org/issue28003 Acknowledgments I thank Guido van Rossum, Victor Stinner, Elvis Pranskevichus, Nathaniel Smith, Łukasz Langa, Andrew Svetlov and many others for their feedback, code reviews, and discussions around this PEP. Copyright This document has been placed in the public domain. ...
...Git, Github, and Phabricator Stufft SR 490 Chain exceptions at C level Stinner IR 496 Environment Markers Polley PR 497 A standard mechanism for backward compatibility Schofield SR 500 A protocol for delegating datetime methods to their ... Belopolsky, Peters IR 502 String Interpolation - Extended Discussion Miller SW 504 Using the System RNG by default Coghlan PR 507 Migrate CPython to Git and GitLab Warsaw SR 510 Specialize functions with guards Stinner SR 511 API for code transformer...
...GitHub only when someone wants to keep working on them. This approach has several issues, but there are also other issues that will need to be addressed regardless of the approach used: Vendor lock-in. GitHub is proprietary and there is risk of vendor lock-in. Their business model might change and they could shut down altogether. For example, several projects decided to move away from GitHub after Microsoft acquisition. If/when the repository is no longer available on GitHub, we will be for...
...gitimately has access to sudo pip install or pip install --user, they can accomplish the same installation entirely outside of Python; if they do not legitimately have such access, that's a problem outside the scope of this PEP. The marker file itself is located in the standard library directory, which is a trusted location (i.e., anyone who can write to the marker file used by a particular installer could, presumably, run arbitrary code inside the installer). Therefore, there is generally no ne...