You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: about.po
+8-26Lines changed: 8 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
# Copyright (C) 2001-2025, Python Software Foundation
3
3
# This file is distributed under the same license as the Python package.
4
4
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
5
-
#
5
+
#
6
6
#,fuzzy
7
7
msgid ""
8
8
msgstr ""
@@ -22,55 +22,37 @@ msgid "About this documentation"
22
22
msgstr""
23
23
24
24
#:../../about.rst:6
25
-
msgid""
26
-
"Python's documentation is generated from `reStructuredText`_ sources using "
27
-
"`Sphinx`_, a documentation generator originally created for Python and now "
28
-
"maintained as an independent project."
25
+
msgid"Python's documentation is generated from `reStructuredText`_ sources using `Sphinx`_, a documentation generator originally created for Python and now maintained as an independent project."
29
26
msgstr""
30
27
31
28
#:../../about.rst:16
32
-
msgid""
33
-
"Development of the documentation and its toolchain is an entirely volunteer "
34
-
"effort, just like Python itself. If you want to contribute, please take a "
35
-
"look at the :ref:`reporting-bugs` page for information on how to do so. New"
36
-
" volunteers are always welcome!"
29
+
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!"
37
30
msgstr""
38
31
39
32
#:../../about.rst:21
40
33
msgid"Many thanks go to:"
41
34
msgstr""
42
35
43
36
#:../../about.rst:23
44
-
msgid""
45
-
"Fred L. Drake, Jr., the creator of the original Python documentation toolset"
46
-
" and author of much of the content;"
37
+
msgid"Fred L. Drake, Jr., the creator of the original Python documentation toolset and author of much of the content;"
47
38
msgstr""
48
39
49
40
#:../../about.rst:25
50
-
msgid""
51
-
"the `Docutils <https://docutils.sourceforge.io/>`_ project for creating "
52
-
"reStructuredText and the Docutils suite;"
41
+
msgid"the `Docutils <https://docutils.sourceforge.io/>`_ project for creating reStructuredText and the Docutils suite;"
53
42
msgstr""
54
43
55
44
#:../../about.rst:27
56
-
msgid""
57
-
"Fredrik Lundh for his Alternative Python Reference project from which Sphinx"
58
-
" got many good ideas."
45
+
msgid"Fredrik Lundh for his Alternative Python Reference project from which Sphinx got many good ideas."
59
46
msgstr""
60
47
61
48
#:../../about.rst:32
62
49
msgid"Contributors to the Python documentation"
63
50
msgstr""
64
51
65
52
#:../../about.rst:34
66
-
msgid""
67
-
"Many people have contributed to the Python language, the Python standard "
68
-
"library, and the Python documentation. See :source:`Misc/ACKS` in the "
69
-
"Python source distribution for a partial list of contributors."
53
+
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."
70
54
msgstr""
71
55
72
56
#:../../about.rst:38
73
-
msgid""
74
-
"It is only with the input and contributions of the Python community that "
75
-
"Python has such wonderful documentation -- Thank You!"
57
+
msgid"It is only with the input and contributions of the Python community that Python has such wonderful documentation -- Thank You!"
"Python is a mature programming language which has established a reputation "
31
-
"for stability. In order to maintain this reputation, the developers would "
32
-
"like to know of any deficiencies you find in Python."
29
+
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."
33
30
msgstr""
34
31
35
32
#:../../bugs.rst:11
36
-
msgid""
37
-
"It can be sometimes faster to fix bugs yourself and contribute patches to "
38
-
"Python as it streamlines the process and involves less people. Learn how to "
39
-
":ref:`contribute <contributing-to-python>`."
33
+
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>`."
40
34
msgstr""
41
35
42
36
#:../../bugs.rst:16
43
37
msgid"Documentation bugs"
44
38
msgstr""
45
39
46
40
#:../../bugs.rst:18
47
-
msgid""
48
-
"If you find a bug in this documentation or would like to propose an "
49
-
"improvement, please submit a bug report on the :ref:`tracker <using-the-"
50
-
"tracker>`. If you have a suggestion on how to fix it, include that as well."
41
+
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."
51
42
msgstr""
52
43
53
44
#:../../bugs.rst:22
54
-
msgid""
55
-
"You can also open a discussion item on our `Documentation Discourse forum "
msgid"If you find a bug in the theme (HTML / CSS / JavaScript) of the documentation, please submit a bug report on the `python-doc-theme bug tracker <https://github.com/python/python-docs-theme>`_."
64
50
msgstr""
65
51
66
52
#:../../bugs.rst:29
67
-
msgid""
68
-
"If you're short on time, you can also email documentation bug reports to "
69
-
"docs@python.org (behavioral bugs can be sent to python-list@python.org). "
70
-
"'docs@' is a mailing list run by volunteers; your request will be noticed, "
71
-
"though it may take a while to be processed."
53
+
msgid"If you're short on time, you can also email documentation bug reports to docs@python.org (behavioral bugs can be sent to python-list@python.org). 'docs@' is a mailing list run by volunteers; your request will be noticed, though it may take a while to be processed."
72
54
msgstr""
73
55
74
56
#:../../bugs.rst:36
75
57
msgid"`Documentation bugs`_"
76
58
msgstr""
77
59
78
60
#:../../bugs.rst:37
79
-
msgid""
80
-
"A list of documentation bugs that have been submitted to the Python issue "
81
-
"tracker."
61
+
msgid"A list of documentation bugs that have been submitted to the Python issue tracker."
"A list of GitHub pages for documentation translation and their primary "
114
-
"contacts."
85
+
msgid"A list of GitHub pages for documentation translation and their primary contacts."
115
86
msgstr""
116
87
117
88
#:../../bugs.rst:52
118
89
msgid"Using the Python issue tracker"
119
90
msgstr""
120
91
121
92
#:../../bugs.rst:54
122
-
msgid""
123
-
"Issue reports for Python itself should be submitted via the GitHub issues "
124
-
"tracker (https://github.com/python/cpython/issues). The GitHub issues "
125
-
"tracker offers a web form which allows pertinent information to be entered "
126
-
"and submitted to the developers."
93
+
msgid"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."
127
94
msgstr""
128
95
129
96
#:../../bugs.rst:59
130
-
msgid""
131
-
"The first step in filing a report is to determine whether the problem has "
132
-
"already been reported. The advantage in doing so, aside from saving the "
133
-
"developers' time, is that you learn what has been done to fix it; it may be "
134
-
"that the problem has already been fixed for the next release, or additional "
135
-
"information is needed (in which case you are welcome to provide it if you "
136
-
"can!). To do this, search the tracker using the search box at the top of the"
137
-
" page."
97
+
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 tracker using the search box at the top of the page."
138
98
msgstr""
139
99
140
100
#:../../bugs.rst:66
141
-
msgid""
142
-
"If the problem you're reporting is not already in the list, log in to "
143
-
"GitHub. If you don't already have a GitHub account, create a new account "
144
-
"using the \"Sign up\" link. It is not possible to submit a bug report "
145
-
"anonymously."
101
+
msgid"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."
146
102
msgstr""
147
103
148
104
#:../../bugs.rst:71
149
-
msgid""
150
-
"Being now logged in, you can submit an issue. Click on the \"New issue\" "
151
-
"button in the top bar to report a new issue."
105
+
msgid"Being now logged in, you can submit an issue. Click on the \"New issue\" button in the top bar to report a new issue."
152
106
msgstr""
153
107
154
108
#:../../bugs.rst:74
155
109
msgid"The submission form has two fields, \"Title\" and \"Comment\"."
156
110
msgstr""
157
111
158
112
#:../../bugs.rst:76
159
-
msgid""
160
-
"For the \"Title\" field, enter a *very* short description of the problem; "
161
-
"fewer than ten words is good."
113
+
msgid"For the \"Title\" field, enter a *very* short description of the problem; fewer than ten words is good."
162
114
msgstr""
163
115
164
116
#:../../bugs.rst:79
165
-
msgid""
166
-
"In the \"Comment\" field, describe the problem in detail, including what you"
167
-
" expected to happen and what did happen. Be sure to include whether any "
168
-
"extension modules were involved, and what hardware and software platform you"
169
-
" were using (including version information as appropriate)."
117
+
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)."
170
118
msgstr""
171
119
172
120
#:../../bugs.rst:84
173
-
msgid""
174
-
"Each issue report will be reviewed by a developer who will determine what "
175
-
"needs to be done to correct the problem. You will receive an update each "
176
-
"time an action is taken on the issue."
121
+
msgid"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."
msgid"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_"
183
126
msgstr""
184
127
185
128
#:../../bugs.rst:92
186
-
msgid""
187
-
"Article which goes into some detail about how to create a useful bug report."
188
-
" This describes what kind of information is useful and why it is useful."
129
+
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."
"Information about writing a good bug report. Some of this is specific to "
200
-
"the Mozilla project, but describes general good practices."
137
+
msgid"Information about writing a good bug report. Some of this is specific to the Mozilla project, but describes general good practices."
201
138
msgstr""
202
139
203
140
#:../../bugs.rst:102
204
141
msgid"Getting started contributing to Python yourself"
205
142
msgstr""
206
143
207
144
#:../../bugs.rst:104
208
-
msgid""
209
-
"Beyond just reporting bugs that you find, you are also welcome to submit "
210
-
"patches to fix them. You can find more information on how to get started "
211
-
"patching Python in the `Python Developer's Guide`_. If you have questions, "
212
-
"the `core-mentorship mailing list`_ is a friendly place to get answers to "
213
-
"any and all questions pertaining to the process of fixing issues in Python."
145
+
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."
Copy file name to clipboardExpand all lines: c-api/abstract.po
+3-11Lines changed: 3 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
# Copyright (C) 2001-2025, Python Software Foundation
3
3
# This file is distributed under the same license as the Python package.
4
4
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
5
-
#
5
+
#
6
6
#,fuzzy
7
7
msgid ""
8
8
msgstr ""
@@ -22,17 +22,9 @@ msgid "Abstract Objects Layer"
22
22
msgstr""
23
23
24
24
#:../../c-api/abstract.rst:9
25
-
msgid""
26
-
"The functions in this chapter interact with Python objects regardless of "
27
-
"their type, or with wide classes of object types (e.g. all numerical types, "
28
-
"or all sequence types). When used on object types for which they do not "
29
-
"apply, they will raise a Python exception."
25
+
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."
30
26
msgstr""
31
27
32
28
#:../../c-api/abstract.rst:14
33
-
msgid""
34
-
"It is not possible to use these functions on objects that are not properly "
35
-
"initialized, such as a list object that has been created by "
36
-
":c:func:`PyList_New`, but whose items have not been set to some non-\\ "
37
-
"``NULL`` value yet."
29
+
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."
Copy file name to clipboardExpand all lines: c-api/allocation.po
+7-35Lines changed: 7 additions & 35 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
# Copyright (C) 2001-2025, Python Software Foundation
3
3
# This file is distributed under the same license as the Python package.
4
4
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
5
-
#
5
+
#
6
6
#,fuzzy
7
7
msgid ""
8
8
msgstr ""
@@ -22,55 +22,27 @@ msgid "Allocating Objects on the Heap"
22
22
msgstr""
23
23
24
24
#:../../c-api/allocation.rst:17
25
-
msgid""
26
-
"Initialize a newly allocated object *op* with its type and initial "
27
-
"reference. Returns the initialized object. Other fields of the object are "
28
-
"not affected."
25
+
msgid"Initialize a newly allocated object *op* with its type and initial reference. Returns the initialized object. Other fields of the object are not affected."
29
26
msgstr""
30
27
31
28
#:../../c-api/allocation.rst:24
32
-
msgid""
33
-
"This does everything :c:func:`PyObject_Init` does, and also initializes the "
34
-
"length information for a variable-size object."
29
+
msgid"This does everything :c:func:`PyObject_Init` does, and also initializes the length information for a variable-size object."
35
30
msgstr""
36
31
37
32
#:../../c-api/allocation.rst:30
38
-
msgid""
39
-
"Allocate a new Python object using the C structure type *TYPE* and the "
40
-
"Python type object *typeobj* (``PyTypeObject*``). Fields not defined by the "
41
-
"Python object header are not initialized. The caller will own the only "
42
-
"reference to the object (i.e. its reference count will be one). The size of "
43
-
"the memory allocation is determined from the "
44
-
":c:member:`~PyTypeObject.tp_basicsize` field of the type object."
33
+
msgid"Allocate a new Python object using the C structure type *TYPE* and the Python type object *typeobj* (``PyTypeObject*``). Fields not defined by the Python object header are not initialized. The caller will own the only reference to the object (i.e. its 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."
45
34
msgstr""
46
35
47
36
#:../../c-api/allocation.rst:41
48
-
msgid""
49
-
"Allocate a new Python object using the C structure type *TYPE* and the "
50
-
"Python type object *typeobj* (``PyTypeObject*``). Fields not defined by the "
51
-
"Python object header are not initialized. The allocated memory allows for "
52
-
"the *TYPE* structure plus *size* (``Py_ssize_t``) fields of the size given "
53
-
"by the :c:member:`~PyTypeObject.tp_itemsize` field of *typeobj*. This is "
54
-
"useful for implementing objects like tuples, which are able to determine "
55
-
"their size at construction time. Embedding the array of fields into the "
56
-
"same allocation decreases the number of allocations, improving the memory "
57
-
"management efficiency."
37
+
msgid"Allocate a new Python object using the C structure type *TYPE* and the Python type object *typeobj* (``PyTypeObject*``). Fields not defined by the Python object header are not initialized. The allocated memory allows for the *TYPE* structure plus *size* (``Py_ssize_t``) fields of the size given by the :c:member:`~PyTypeObject.tp_itemsize` field of *typeobj*. 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."
58
38
msgstr""
59
39
60
40
#:../../c-api/allocation.rst:55
61
-
msgid""
62
-
"Releases memory allocated to an object using :c:macro:`PyObject_New` or "
63
-
":c:macro:`PyObject_NewVar`. This is normally called from the "
64
-
":c:member:`~PyTypeObject.tp_dealloc` handler specified in the object's type."
65
-
" The fields of the object should not be accessed after this call as the "
66
-
"memory is no longer a valid Python object."
41
+
msgid"Releases memory allocated to an object using :c:macro:`PyObject_New` or :c:macro:`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."
67
42
msgstr""
68
43
69
44
#:../../c-api/allocation.rst:64
70
-
msgid""
71
-
"Object which is visible in Python as ``None``. This should only be accessed"
72
-
" using the :c:macro:`Py_None` macro, which evaluates to a pointer to this "
73
-
"object."
45
+
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."
0 commit comments