GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||
GeezerVison is showing github.com — use Git/git instead of Mercurial/hg by matrixise · Pull Request #67 · python/devguide Conversation
Member
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
This was referenced
|
There was an error while loading. Please reload this page.
|
Can you do this against the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
yep, I will propose to the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You can try changing the base branch directly in this PR, but I didn't want to do it for you in case there were conflicts. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I think there will be some conflicts, because there is a diff between master and github |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| CPython is developed using `Git <https://git-scm.com/>`_. The Git command line | ||
| program is named ``git``; this is also used to refer to Git itself. Git is | ||
| easily available for common Unix systems by way of the standard package manager; | ||
| under Windows, you might want to use the `TortoiseGit <http://tortoisegit.org/>`_ |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It might be worth also linking to https://desktop.github.com/ as well at TortoiseGit.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
sure, we have some possibilities for a desktop interface for Git.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@matrixise did you want to resolve the conflicts in this PR? Otherwise I can revert the changes in setup.rst so I can merge this PR. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I forked this PR so that the work @matrixise did could be used to close out the last GitHub migration milestone bug! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Co-Authored-By: Tim Peters <[email protected]> Co-Authored-By: Terry Jan Reedy <[email protected]> Co-authored-by: Brett Cannon <[email protected]>
In order to resolve issues python#652 and python#653 in the devguide (which are duplicates of each other), we added a theme variable to `python_docs_theme/layout.html` in PR python#67. This will allow all users of the python-docs-theme library to have more functionality and backwards compatibility. In addition, if users don't define a link for copyright information, then they won't have a broken link that leads to nowhere in their page footer. In order to have the correct copyright link for the devguide specifically, we just needed to specify it in the `html_theme_options` dictionary in the devguide's `conf.py`, which I did in this commit.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.