Creat bump-up.yml actions

Author: cocoatomo

Doc/locales/.tx/config

@@ -0,0 +1,57 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2001-2021, Python Software Foundation
+# This file is distributed under the same license as the Python package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Python 3.10\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2021-06-27 21:31+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <[email protected]>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../about.rst:3
+msgid "About these documents"
+msgstr ""
+
+#: ../../about.rst:6
+msgid "These documents are generated from `reStructuredText`_ sources by `Sphinx`_, a document processor specifically written for the Python documentation."
+msgstr ""
+
+#: ../../about.rst:15
+msgid "Development of the documentation and its toolchain is an entirely volunteer effort, just like Python itself.  If you want to contribute, please take a look at the :ref:`reporting-bugs` page for information on how to do so.  New volunteers are always welcome!"
+msgstr ""
+
+#: ../../about.rst:20
+msgid "Many thanks go to:"
+msgstr ""
+
+#: ../../about.rst:22
+msgid "Fred L. Drake, Jr., the creator of the original Python documentation toolset and writer of much of the content;"
+msgstr ""
+
+#: ../../about.rst:24
+msgid "the `Docutils <http://docutils.sourceforge.net/>`_ project for creating reStructuredText and the Docutils suite;"
+msgstr ""
+
+#: ../../about.rst:26
+msgid "Fredrik Lundh for his `Alternative Python Reference <http://effbot.org/zone/pyref.htm>`_ project from which Sphinx got many good ideas."
+msgstr ""
+
+#: ../../about.rst:32
+msgid "Contributors to the Python Documentation"
+msgstr ""
+
+#: ../../about.rst:34
+msgid "Many people have contributed to the Python language, the Python standard library, and the Python documentation.  See :source:`Misc/ACKS` in the Python source distribution for a partial list of contributors."
+msgstr ""
+
+#: ../../about.rst:38
+msgid "It is only with the input and contributions of the Python community that Python has such wonderful documentation -- Thank You!"
+msgstr ""

Doc/locales/pot/about.pot

@@ -0,0 +1,121 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2001-2021, Python Software Foundation
+# This file is distributed under the same license as the Python package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Python 3.10\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2021-06-27 21:31+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <[email protected]>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../bugs.rst:5
+msgid "Dealing with Bugs"
+msgstr ""
+
+#: ../../bugs.rst:7
+msgid "Python is a mature programming language which has established a reputation for stability.  In order to maintain this reputation, the developers would like to know of any deficiencies you find in Python."
+msgstr ""
+
+#: ../../bugs.rst:11
+msgid "It can be sometimes faster to fix bugs yourself and contribute patches to Python as it streamlines the process and involves less people. Learn how to :ref:`contribute <contributing-to-python>`."
+msgstr ""
+
+#: ../../bugs.rst:16
+msgid "Documentation bugs"
+msgstr ""
+
+#: ../../bugs.rst:18
+msgid "If you find a bug in this documentation or would like to propose an improvement, please submit a bug report on the :ref:`tracker <using-the-tracker>`.  If you have a suggestion on how to fix it, include that as well."
+msgstr ""
+
+#: ../../bugs.rst:22
+msgid "If you're short on time, you can also email documentation bug reports to [email protected] (behavioral bugs can be sent to [email protected]). 'docs@' is a mailing list run by volunteers; your request will be noticed, though it may take a while to be processed."
+msgstr ""
+
+#: ../../bugs.rst:30
+msgid "`Documentation bugs`_"
+msgstr ""
+
+#: ../../bugs.rst:30
+msgid "A list of documentation bugs that have been submitted to the Python issue tracker."
+msgstr ""
+
+#: ../../bugs.rst:33
+msgid "`Issue Tracking <https://devguide.python.org/tracker/>`_"
+msgstr ""
+
+#: ../../bugs.rst:33
+msgid "Overview of the process involved in reporting an improvement on the tracker."
+msgstr ""
+
+#: ../../bugs.rst:35
+msgid "`Helping with Documentation <https://devguide.python.org/docquality/#helping-with-documentation>`_"
+msgstr ""
+
+#: ../../bugs.rst:36
+msgid "Comprehensive guide for individuals that are interested in contributing to Python documentation."
+msgstr ""
+
+#: ../../bugs.rst:41
+msgid "Using the Python issue tracker"
+msgstr ""
+
+#: ../../bugs.rst:43
+msgid "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."
+msgstr ""
+
+#: ../../bugs.rst:47
+msgid "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 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."
+msgstr ""
+
+#: ../../bugs.rst:54
+msgid "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."
+msgstr ""
+
+#: ../../bugs.rst:59
+msgid "Being now logged in, you can submit a bug.  Select the \"Create New\" link in the sidebar to open the bug reporting form."
+msgstr ""
+
+#: ../../bugs.rst:62
+msgid "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."
+msgstr ""
+
+#: ../../bugs.rst:67
+msgid "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)."
+msgstr ""
+
+#: ../../bugs.rst:72
+msgid "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."
+msgstr ""
+
+#: ../../bugs.rst:81
+msgid "`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_"
+msgstr ""
+
+#: ../../bugs.rst:80
+msgid "Article which goes into some detail about how to create a useful bug report. This describes what kind of information is useful and why it is useful."
+msgstr ""
+
+#: ../../bugs.rst:84
+msgid "`Bug Report Writing Guidelines <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>`_"
+msgstr ""
+
+#: ../../bugs.rst:84
+msgid "Information about writing a good bug report.  Some of this is specific to the Mozilla project, but describes general good practices."
+msgstr ""
+
+#: ../../bugs.rst:90
+msgid "Getting started contributing to Python yourself"
+msgstr ""
+
+#: ../../bugs.rst:92
+msgid "Beyond just reporting bugs that you find, you are also welcome to submit patches to fix them.  You can find more information on how to get started 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."
+msgstr ""

Doc/locales/pot/bugs.pot

@@ -0,0 +1,29 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2001-2021, Python Software Foundation
+# This file is distributed under the same license as the Python package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Python 3.10\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2021-06-27 21:31+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <[email protected]>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../c-api/abstract.rst:7
+msgid "Abstract Objects Layer"
+msgstr ""
+
+#: ../../c-api/abstract.rst:9
+msgid "The functions in this chapter interact with Python objects regardless of their type, or with wide classes of object types (e.g. all numerical types, or all sequence types).  When used on object types for which they do not apply, they will raise a Python exception."
+msgstr ""
+
+#: ../../c-api/abstract.rst:14
+msgid "It is not possible to use these functions on objects that are not properly initialized, such as a list object that has been created by :c:func:`PyList_New`, but whose items have not been set to some non-\\ ``NULL`` value yet."
+msgstr ""

Doc/locales/pot/c-api/abstract.pot

@@ -0,0 +1,53 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2001-2021, Python Software Foundation
+# This file is distributed under the same license as the Python package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Python 3.10\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2021-06-27 21:31+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <[email protected]>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../c-api/allocation.rst:6
+msgid "Allocating Objects on the Heap"
+msgstr ""
+
+#: ../../c-api/allocation.rst:17
+msgid "Initialize a newly-allocated object *op* with its type and initial reference.  Returns the initialized object.  If *type* indicates that the object participates in the cyclic garbage detector, it is added to the detector's set of observed objects. Other fields of the object are not affected."
+msgstr ""
+
+#: ../../c-api/allocation.rst:26
+msgid "This does everything :c:func:`PyObject_Init` does, and also initializes the length information for a variable-size object."
+msgstr ""
+
+#: ../../c-api/allocation.rst:32
+msgid "Allocate a new Python object using the C structure type *TYPE* and the Python type object *type*.  Fields not defined by the Python object header are not initialized; the object's reference count will be one.  The size of the memory allocation is determined from the :c:member:`~PyTypeObject.tp_basicsize` field of the type object."
+msgstr ""
+
+#: ../../c-api/allocation.rst:41
+msgid "Allocate a new Python object using the C structure type *TYPE* and the Python type object *type*.  Fields not defined by the Python object header are not initialized.  The allocated memory allows for the *TYPE* structure plus *size* fields of the size given by the :c:member:`~PyTypeObject.tp_itemsize` field of *type*.  This is useful for implementing objects like tuples, which are able to determine their size at construction time.  Embedding the array of fields into the same allocation decreases the number of allocations, improving the memory management efficiency."
+msgstr ""
+
+#: ../../c-api/allocation.rst:53
+msgid "Releases memory allocated to an object using :c:func:`PyObject_New` or :c:func:`PyObject_NewVar`.  This is normally called from the :c:member:`~PyTypeObject.tp_dealloc` handler specified in the object's type.  The fields of the object should not be accessed after this call as the memory is no longer a valid Python object."
+msgstr ""
+
+#: ../../c-api/allocation.rst:62
+msgid "Object which is visible in Python as ``None``.  This should only be accessed using the :c:macro:`Py_None` macro, which evaluates to a pointer to this object."
+msgstr ""
+
+#: ../../c-api/allocation.rst:69
+msgid ":c:func:`PyModule_Create`"
+msgstr ""
+
+#: ../../c-api/allocation.rst:70
+msgid "To allocate and create extension modules."
+msgstr ""