Merge branch 'main' of github.com:python/cpython

Author: rhettinger

.gitattributes

@@ -22,23 +22,27 @@ Lib/test/sndhdrdata/sndhdr.* binary
 PC/classicAppCompat.* binary
 
 # Text files that should not be subject to eol conversion
-Lib/test/cjkencodings/* -text
-Lib/test/decimaltestdata/*.decTest -text
-Lib/test/test_email/data/*.txt -text
-Lib/test/xmltestdata/* -text
-Lib/test/coding20731.py -text
-Lib/test/test_importlib/data01/* -text
-Lib/test/test_importlib/namespacedata01/* -text
+[attr]noeol -text
+
+Lib/test/cjkencodings/*                    noeol
+Lib/test/coding20731.py                    noeol
+Lib/test/decimaltestdata/*.decTest         noeol
+Lib/test/test_email/data/*.txt             noeol
+Lib/test/test_importlib/data01/*           noeol
+Lib/test/test_importlib/namespacedata01/*  noeol
+Lib/test/xmltestdata/*                     noeol
 
 # CRLF files
-*.bat text eol=crlf
-*.ps1 text eol=crlf
-*.sln text eol=crlf
-*.vcxproj* text eol=crlf
-*.props text eol=crlf
-*.proj text eol=crlf
-PCbuild/readme.txt text eol=crlf
-PC/readme.txt text eol=crlf
+[attr]dos text eol=crlf
+
+*.bat               dos
+*.proj              dos
+*.props             dos
+*.ps1               dos
+*.sln               dos
+*.vcxproj*          dos
+PC/readme.txt       dos
+PCbuild/readme.txt  dos
 
 # Language aware diff headers
 # https://tekin.co.uk/2020/10/better-git-diff-output-for-ruby-python-elixir-and-more

.github/CONTRIBUTING.rst

@@ -44,7 +44,7 @@ comments they leave and their "Details" links, respectively. The key points of
 our workflow that are not covered by a bot or status check are:
 
 - All discussions that are not directly related to the code in the pull request
-  should happen on bugs.python.org
+  should happen on `GitHub Issues <https://github.com/python/cpython/issues>`_.
 - Upon your first non-trivial pull request (which includes documentation changes),
   feel free to add yourself to ``Misc/ACKS``
 

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Submit a bug report
+labels: "type-bug"
+---
+
+<!--
+  If you're new to Python and you're not sure whether what you're experiencing is a bug, the CPython issue tracker is not
+  the right place to seek help. Consider the following options instead:
+
+  - reading the Python tutorial: https://docs.python.org/3/tutorial/
+  - posting in the "Users" category on discuss.python.org: https://discuss.python.org/c/users/7
+  - emailing the Python-list mailing list: https://mail.python.org/mailman/listinfo/python-list
+  - searching our issue tracker (https://github.com/python/cpython/issues) to see if
+    your problem has already been reported
+-->
+
+**Bug report**
+
+A clear and concise description of what the bug is.
+Include a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example), if possible.
+
+**Your environment**
+
+<!-- Include as many relevant details as possible about the environment you experienced the bug in -->
+
+- CPython versions tested on:
+- Operating system and architecture:
+
+<!--
+You can freely edit this text. Remove any lines you believe are unnecessary.
+-->

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,7 @@
-blank_issues_enabled: false
 contact_links:
-  - name: ⚠ GitHub Issues Migration in progress ⚠
-    url: https://discuss.python.org/t/github-issues-migration-status-update/14573
-    about: Check status updates on the migration
+  - name: "Getting help"
+    about: "Ask questions about using Python and debugging errors on Discourse."
+    url: "https://discuss.python.org/c/users/7"
+  - name: "Proposing new features"
+    about: "Submit major feature proposal (e.g. syntax changes) to an ideas forum first."
+    url: "https://discuss.python.org/c/ideas/6"

.github/ISSUE_TEMPLATE/crash.md

@@ -0,0 +1,33 @@
+---
+name: Crash report
+about: A hard crash of the interpreter, possibly with a core dump
+labels: "type-crash"
+---
+
+<!--
+  Use this template for hard crashes of the interpreter, segmentation faults, failed C-level assertions, and similar.
+  Do not submit this form if you encounter an exception being unexpectedly raised from a Python function.
+  Most of the time, these should be filed as bugs, rather than crashes.
+
+  The CPython interpreter is itself written in a different programming language, C.
+  For CPython, a "crash" is when Python itself fails, leading to a traceback in the C stack.
+-->
+
+**Crash report**
+
+Tell us what happened, ideally including a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example).
+
+**Error messages**
+
+Enter any relevant error message caused by the crash, including a core dump if there is one.
+
+**Your environment**
+
+<!-- Include as many relevant details as possible about the environment you experienced the bug in -->
+
+- CPython versions tested on:
+- Operating system and architecture:
+
+<!--
+You can freely edit this text. Remove any lines you believe are unnecessary.
+-->

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,9 @@
+---
+name: Documentation
+about: Report a problem with the documentation
+labels: "docs"
+---
+
+**Documentation**
+
+(A clear and concise description of the issue.)

.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,28 @@
+---
+name: Feature or enhancement
+about: Submit a proposal for a new CPython feature or enhancement
+labels: "type-feature"
+---
+
+**Feature or enhancement**
+
+(A clear and concise description of your proposal.)
+
+**Pitch**
+
+(Explain why this feature or enhacement should be implemented and how it would be used.
+ Add examples, if applicable.)
+
+**Previous discussion**
+
+<!--
+  New features to Python should first be discussed elsewhere before creating issues on GitHub,
+  for example in the "ideas" category (https://discuss.python.org/c/ideas/6) of discuss.python.org,
+  or the python-ideas mailing list (https://mail.python.org/mailman3/lists/python-ideas.python.org/).
+  Use this space to post links to the places where you have already discussed this feature proposal:
+-->
+
+
+<!--
+You can freely edit this text. Remove any lines you believe are unnecessary.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -7,10 +7,10 @@ Please read this comment in its entirety. It's quite important.
 It should be in the following format:
 
 ```
-bpo-NNNN: Summary of the changes made
+gh-NNNNN: Summary of the changes made
 ```
 
-Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.
+Where: gh-NNNNN refers to the GitHub issue number.
 
 Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.
 

.github/workflows/build.yml

@@ -1,6 +1,6 @@
 name: Tests
 
-# bpo-40548: "paths-ignore" is not used to skip documentation-only PRs, because
+# gh-84728: "paths-ignore" is not used to skip documentation-only PRs, because
 # it prevents to mark a job as mandatory. A PR cannot be merged if a job is
 # mandatory but not scheduled because of "paths-ignore".
 on:

.github/workflows/new-bugs-announce-notifier.yml

@@ -0,0 +1,53 @@
+name: new-bugs-announce notifier
+
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  notify-new-bugs-announce:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14
+      - run: npm install mailgun.js form-data
+      - name: Send notification
+        uses: actions/github-script@v5
+        env:
+          MAILGUN_API_KEY: ${{ secrets.PSF_MAILGUN_KEY }}
+        with:
+          script: |
+            const Mailgun = require("mailgun.js");
+            const formData = require('form-data');
+            const mailgun = new Mailgun(formData);
+            const DOMAIN = "mg.python.org";
+            const mg = mailgun.client({username: 'api', key: process.env.MAILGUN_API_KEY});
+            github.rest.issues.get({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+            })
+            .then(function(issue) {
+              const payload = {
+                author : issue.data.user.login,
+                issue  : issue.data.number,
+                title  : issue.data.title,
+                url    : issue.data.html_url,
+                labels : issue.data.labels.map(label => { return label.name }).join(", "),
+                assignee : issue.data.assignees.map(assignee => { return assignee.login }),
+                body   : issue.data.body
+              };
+            
+              const data = {
+                from: "CPython Issues <[email protected]>",
+                to: "[email protected]",
+                subject: `[Issue ${issue.data.number}] ${issue.data.title}`,
+                template: "new-github-issue",
+                'o:tracking-clicks': 'no',
+                'h:X-Mailgun-Variables': JSON.stringify(payload)
+              };
+              return mg.messages.create(DOMAIN, data)
+            })
+            .then(msg => console.log(msg));

.github/workflows/stale.yml

@@ -14,27 +14,13 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - name: "Check PRs with 'CLA signed' label"
+    - name: "Check PRs"
       uses: actions/stale@v4
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
-        only-pr-labels: 'CLA signed'
         stale-pr-message: 'This PR is stale because it has been open for 30 days with no activity.'
         stale-pr-label: 'stale'
         days-before-stale: 30
         days-before-close: -1
         ascending: true
         operations-per-run: 120
-
-    - name: "Check PRs with 'CLA not signed' label"
-      uses: actions/stale@v4
-      with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
-        only-pr-labels: 'CLA not signed'
-        stale-pr-message: 'This PR is stale because it has been open for 30 days with no activity. If the CLA is not signed within 14 days, it will be closed. See also https://devguide.python.org/pullrequest/#licensing'
-        stale-pr-label: 'stale'
-        close-pr-message: 'Closing this stale PR because the CLA is still not signed.'
-        days-before-stale: 30
-        days-before-close: 14
-        ascending: true
-        operations-per-run: 120

Doc/bugs.rst

@@ -35,43 +35,48 @@ though it may take a while to be processed.
    `Helping with Documentation <https://devguide.python.org/docquality/#helping-with-documentation>`_
       Comprehensive guide for individuals that are interested in contributing to Python documentation.
 
+   `Documentation Translations <https://devguide.python.org/documenting/#translating>`_
+      A list of GitHub pages for documentation translation and their primary contacts.
+
+
 .. _using-the-tracker:
 
 Using the Python issue tracker
 ==============================
 
-Bug reports for Python itself should be submitted via the Python Bug Tracker
-(https://bugs.python.org/).  The bug tracker offers a web form which allows
-pertinent information to be entered and submitted to the developers.
+Issue reports for Python itself should be submitted via the GitHub issues
+tracker (https://github.com/python/cpython/issues).
+The GitHub issues tracker offers a web form which allows pertinent information
+to be entered and submitted to the developers.
 
 The first step in filing a report is to determine whether the problem has
 already been reported.  The advantage in doing so, aside from saving the
-developers time, is that you learn what has been done to fix it; it may be that
+developers' time, is that you learn what has been done to fix it; it may be that
 the problem has already been fixed for the next release, or additional
 information is needed (in which case you are welcome to provide it if you can!).
-To do this, search the bug database using the search box on the top of the page.
+To do this, search the tracker using the search box at the top of the page.
+
+If the problem you're reporting is not already in the list, log in to GitHub.
+If you don't already have a GitHub account, create a new account using the
+"Sign up" link.
+It is not possible to submit a bug report anonymously.
 
-If the problem you're reporting is not already in the bug tracker, go back to
-the Python Bug Tracker and log in.  If you don't already have a tracker account,
-select the "Register" link or, if you use OpenID, one of the OpenID provider
-logos in the sidebar.  It is not possible to submit a bug report anonymously.
+Being now logged in, you can submit an issue.
+Click on the "New issue" button in the top bar to report a new issue.
 
-Being now logged in, you can submit a bug.  Select the "Create New" link in the
-sidebar to open the bug reporting form.
+The submission form has two fields, "Title" and "Comment".
 
-The submission form has a number of fields.  For the "Title" field, enter a
-*very* short description of the problem; less than ten words is good.  In the
-"Type" field, select the type of your problem; also select the "Component" and
-"Versions" to which the bug relates.
+For the "Title" field, enter a *very* short description of the problem;
+less than ten words is good.
 
 In the "Comment" field, describe the problem in detail, including what you
 expected to happen and what did happen.  Be sure to include whether any
 extension modules were involved, and what hardware and software platform you
 were using (including version information as appropriate).
 
-Each bug report will be assigned to a developer who will determine what needs to
-be done to correct the problem.  You will receive an update each time action is
-taken on the bug.
+Each issue report will be reviewed by a developer who will determine what needs to
+be done to correct the problem. You will receive an update each time an action is
+taken on the issue.
 
 
 .. seealso::
@@ -95,6 +100,6 @@ patching Python in the `Python Developer's Guide`_.  If you have questions,
 the `core-mentorship mailing list`_ is a friendly place to get answers to
 any and all questions pertaining to the process of fixing issues in Python.
 
-.. _Documentation bugs: https://bugs.python.org/issue?@filter=status&@filter=components&components=4&status=1&@columns=id,activity,title,status&@sort=-activity
+.. _Documentation bugs: https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocs
 .. _Python Developer's Guide: https://devguide.python.org/
 .. _core-mentorship mailing list: https://mail.python.org/mailman3/lists/core-mentorship.python.org/