-
-
Notifications
You must be signed in to change notification settings - Fork 23
Expand file tree
/
Copy pathcporting.po
More file actions
49 lines (44 loc) · 1.46 KB
/
cporting.po
File metadata and controls
49 lines (44 loc) · 1.46 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2024, 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.12\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-12-04 09:48+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: howto/cporting.rst:7
msgid "Porting Extension Modules to Python 3"
msgstr ""
#: howto/cporting.rst:9
msgid ""
"We recommend the following resources for porting extension modules to Python "
"3:"
msgstr ""
#: howto/cporting.rst:11
msgid ""
"The `Migrating C extensions`_ chapter from *Supporting Python 3: An in-depth "
"guide*, a book on moving from Python 2 to Python 3 in general, guides the "
"reader through porting an extension module."
msgstr ""
#: howto/cporting.rst:15
msgid ""
"The `Porting guide`_ from the *py3c* project provides opinionated "
"suggestions with supporting code."
msgstr ""
#: howto/cporting.rst:17
msgid ""
":ref:`Recommended third party tools <c-api-tools>` offer abstractions over "
"the Python's C API. Extensions generally need to be re-written to use one of "
"them, but the library then handles differences between various Python "
"versions and implementations."
msgstr ""