# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR , YEAR.
#
# Translators:
# python-doc bot, 2025
# b785ccb154ea7c5e4722f287fb17d327_f3b4082, 2026
# Inada Naoki , 2026
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-10-23 18:01+0000\n"
"PO-Revision-Date: 2025-09-16 00:02+0000\n"
"Last-Translator: Inada Naoki , 2026\n"
"Language-Team: Japanese (https://app.transifex.com/python-doc/teams/5390/"
"ja/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ja\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: ../../using/ios.rst:5
msgid "Using Python on iOS"
msgstr "iOS Python "
#: ../../using/ios.rst:0
msgid "Authors"
msgstr ""
#: ../../using/ios.rst:8
msgid "Russell Keith-Magee (2024-03)"
msgstr "Russell Keith-Magee (2024-03)"
#: ../../using/ios.rst:10
msgid ""
"Python on iOS is unlike Python on desktop platforms. On a desktop platform, "
"Python is generally installed as a system resource that can be used by any "
"user of that computer. Users then interact with Python by running a :program:"
"`python` executable and entering commands at an interactive prompt, or by "
"running a Python script."
msgstr ""
"iOS Python Python "
" Python "
""
" :program:`python` "
" Python Python "
""
#: ../../using/ios.rst:16
msgid ""
"On iOS, there is no concept of installing as a system resource. The only "
"unit of software distribution is an \"app\". There is also no console where "
"you could run a :program:`python` executable, or interact with a Python REPL."
msgstr ""
"iOS "
" \"\" :program:`python` "
" Python REPL "
""
#: ../../using/ios.rst:20
msgid ""
"As a result, the only way you can use Python on iOS is in embedded mode - "
"that is, by writing a native iOS application, and embedding a Python "
"interpreter using ``libPython``, and invoking Python code using the :ref:"
"`Python embedding API `. The full Python interpreter, the "
"standard library, and all your Python code is then packaged as a standalone "
"bundle that can be distributed via the iOS App Store."
msgstr ""
" Python iOS "
" iOS ``libPython`` Python "
" :ref:`Python API ` "
" Python Python "
" Python iOS App Store "
""
msgid ""
"If you're looking to experiment for the first time with writing an iOS app "
"in Python, projects such as `BeeWare `__, `Kivy "
"`__, and `Flet `__ will provide a much "
"more approachable user experience. These projects manage the complexities "
"associated with getting an iOS project running, so you only need to deal "
"with the Python code itself."
msgstr ""
"Python iOS `BeeWare `__`Kivy `__`Flet `__ "
"\n"
" iOS "
"Python "
#: ../../using/ios.rst:34
msgid "Python at runtime on iOS"
msgstr "iOS Python"
#: ../../using/ios.rst:37
msgid "iOS version compatibility"
msgstr "iOS "
#: ../../using/ios.rst:39
msgid ""
"The minimum supported iOS version is specified at compile time, using the :"
"option:`--host` option to ``configure``. By default, when compiled for iOS, "
"Python will be compiled with a minimum supported iOS version of 13.0. To use "
"a different minimum iOS version, provide the version number as part of the :"
"option:`!--host` argument - for example, ``--host=arm64-apple-ios15.4-"
"simulator`` would compile an ARM64 simulator build with a deployment target "
"of 15.4."
msgstr ""
" iOS ``configure`` :"
"option:`--host` iOS "
" Python 13.0 iOS "
" iOS :option:`!--"
"host` ``--host=arm64-"
"apple-ios15.4-simulator`` ARM64 "
"Deployment Target 15.4 "
#: ../../using/ios.rst:48
msgid "Platform identification"
msgstr ""
#: ../../using/ios.rst:50
msgid ""
"When executing on iOS, ``sys.platform`` will report as ``ios``. This value "
"will be returned on an iPhone or iPad, regardless of whether the app is "
"running on the simulator or a physical device."
msgstr ""
"iOS ``sys.platform`` ``ios`` "
" "
"iPhone iPad "
#: ../../using/ios.rst:54
msgid ""
"Information about the specific runtime environment, including the iOS "
"version, device model, and whether the device is a simulator, can be "
"obtained using :func:`platform.ios_ver`. :func:`platform.system` will report "
"``iOS`` or ``iPadOS``, depending on the device."
msgstr ""
"iOS "
" :func:`platform.ios_ver` "
" :func:`platform.system` ``iOS`` "
"``iPadOS`` "
#: ../../using/ios.rst:59
msgid ""
":func:`os.uname` reports kernel-level details; it will report a name of "
"``Darwin``."
msgstr ""
":func:`os.uname` ``Darwin`` "
""
#: ../../using/ios.rst:63
msgid "Standard library availability"
msgstr ""
#: ../../using/ios.rst:65
msgid ""
"The Python standard library has some notable omissions and restrictions on "
"iOS. See the :ref:`API availability guide for iOS ` for "
"details."
msgstr ""
"Python iOS "
" :ref:`iOS API ` "
""
#: ../../using/ios.rst:70
msgid "Binary extension modules"
msgstr ""
#: ../../using/ios.rst:72
msgid ""
"One notable difference about iOS as a platform is that App Store "
"distribution imposes hard requirements on the packaging of an application. "
"One of these requirements governs how binary extension modules are "
"distributed."
msgstr ""
" iOS App Store "
" "
""
#: ../../using/ios.rst:76
msgid ""
"The iOS App Store requires that *all* binary modules in an iOS app must be "
"dynamic libraries, contained in a framework with appropriate metadata, "
"stored in the ``Frameworks`` folder of the packaged app. There can be only a "
"single binary per framework, and there can be no executable binary material "
"outside the ``Frameworks`` folder."
msgstr ""
"iOS App Store iOS "
" ``Frameworks`` "
""
" ``Frameworks`` "
""
#: ../../using/ios.rst:82
msgid ""
"This conflicts with the usual Python approach for distributing binaries, "
"which allows a binary extension module to be loaded from any location on "
"``sys.path``. To ensure compliance with App Store policies, an iOS project "
"must post-process any Python packages, converting ``.so`` binary modules "
"into individual standalone frameworks with appropriate metadata and signing. "
"For details on how to perform this post-processing, see the guide for :ref:"
"`adding Python to your project `."
msgstr ""
" ``sys.path`` "
" Python App "
"Store iOS Python "
" ``.so`` "
""
" :ref:` Python ` "
msgid ""
"To help Python discover binaries in their new location, the original ``.so`` "
"file on ``sys.path`` is replaced with a ``.fwork`` file. This file is a text "
"file containing the location of the framework binary, relative to the app "
"bundle. To allow the framework to resolve back to the original location, the "
"framework must contain a ``.origin`` file that contains the location of the "
"``.fwork`` file, relative to the app bundle."
msgstr ""
"Python ``sys.path`` ``.so`` "
" ``.fwork`` \n"
""
"\n"
" "
"``.origin`` \n"
" ``.fwork`` "
""
#: ../../using/ios.rst:97
msgid ""
"For example, consider the case of an import ``from foo.bar import _whiz``, "
"where ``_whiz`` is implemented with the binary module ``sources/foo/bar/"
"_whiz.abi3.so``, with ``sources`` being the location registered on ``sys."
"path``, relative to the application bundle. This module *must* be "
"distributed as ``Frameworks/foo.bar._whiz.framework/foo.bar._whiz`` "
"(creating the framework name from the full import path of the module), with "
"an ``Info.plist`` file in the ``.framework`` directory identifying the "
"binary as a framework. The ``foo.bar._whiz`` module would be represented in "
"the original location with a ``sources/foo/bar/_whiz.abi3.fwork`` marker "
"file, containing the path ``Frameworks/foo.bar._whiz/foo.bar._whiz``. The "
"framework would also contain ``Frameworks/foo.bar._whiz.framework/foo.bar."
"_whiz.origin``, containing the path to the ``.fwork`` file."
msgstr ""
"``from foo.bar import _whiz`` "
" ``_whiz`` ``sources/foo/bar/_whiz.abi3.so`` "
" ``sources`` ``sys."
"path`` ``Frameworks/foo.bar._whiz."
"framework/foo.bar._whiz`` ("
") ``Info."
"plist`` ``.framework`` "
" ``foo.bar._whiz`` ``Frameworks/foo.bar."
"_whiz/foo.bar._whiz`` ``sources/foo/bar/_whiz.abi3.fwork`` "
" ``.fwork`` "
" ``Frameworks/foo.bar._whiz.framework/foo.bar._whiz.origin`` "
""
msgid ""
"When running on iOS, the Python interpreter will install an :class:"
"`~importlib.machinery.AppleFrameworkLoader` that is able to read and import "
"``.fwork`` files. Once imported, the ``__file__`` attribute of the binary "
"module will report as the location of the ``.fwork`` file. However, the :"
"class:`~importlib.machinery.ModuleSpec` for the loaded module will report "
"the ``origin`` as the location of the binary in the framework folder."
msgstr ""
"iOS Python ``.fwork`` "
" :class:`~importlib.machinery.AppleFrameworkLoader` "
"\n"
" ``__file__`` ``.fwork`` "
"\n"
" :class:`~importlib.machinery.ModuleSpec` "
"``origin`` "
#: ../../using/ios.rst:118
msgid "Compiler stub binaries"
msgstr ""
msgid ""
"Xcode doesn't expose explicit compilers for iOS; instead, it uses an "
"``xcrun`` script that resolves to a full compiler path (e.g., ``xcrun --sdk "
"iphoneos clang`` to get the ``clang`` for an iPhone device). However, using "
"this script poses two problems:"
msgstr ""
"Xcode iOS "
" ``xcrun`` ( ``xcrun --"
"sdk iphoneos clang`` iPhone ``clang`` ) "
"2:"
#: ../../using/ios.rst:125
msgid ""
"The output of ``xcrun`` includes paths that are machine specific, resulting "
"in a sysconfig module that cannot be shared between users; and"
msgstr ""
"``xcrun`` sysconfig "
""
msgid ""
"It results in ``CC``/``CPP``/``LD``/``AR`` definitions that include spaces. "
"There is a lot of C ecosystem tooling that assumes that you can split a "
"command line at the first space to get the path to the compiler executable; "
"this isn't the case when using ``xcrun``."
msgstr ""
"``CC``/``CPP``/``LD``/``AR`` \n"
"C "
"\n"
"``xcrun`` "
#: ../../using/ios.rst:133
msgid ""
"To avoid these problems, Python provided stubs for these tools. These stubs "
"are shell script wrappers around the underingly ``xcrun`` tools, distributed "
"in a ``bin`` folder distributed alongside the compiled iOS framework. These "
"scripts are relocatable, and will always resolve to the appropriate local "
"system paths. By including these scripts in the bin folder that accompanies "
"a framework, the contents of the ``sysconfig`` module becomes useful for end-"
"users to compile their own modules. When compiling third-party Python "
"modules for iOS, you should ensure these stub binaries are on your path."
msgstr ""
" Python "
" iOS "
"``bin`` ``xcrun`` "
""
" bin "
" ``sysconfig`` "
"iOS Python "
""
#: ../../using/ios.rst:143
msgid "Installing Python on iOS"
msgstr "iOS Python "
#: ../../using/ios.rst:146
msgid "Tools for building iOS apps"
msgstr "iOS "
#: ../../using/ios.rst:148
msgid ""
"Building for iOS requires the use of Apple's Xcode tooling. It is strongly "
"recommended that you use the most recent stable release of Xcode. This will "
"require the use of the most (or second-most) recently released macOS "
"version, as Apple does not maintain Xcode for older macOS versions. The "
"Xcode Command Line Tools are not sufficient for iOS development; you need a "
"*full* Xcode install."
msgstr ""
"iOS Apple Xcode Xcode "
"Apple macOS "
" Xcode () "
" macOS Xcode iOS "
" Xcode "
#: ../../using/ios.rst:155
msgid ""
"If you want to run your code on the iOS simulator, you'll also need to "
"install an iOS Simulator Platform. You should be prompted to select an iOS "
"Simulator Platform when you first run Xcode. Alternatively, you can add an "
"iOS Simulator Platform by selecting from the Platforms tab of the Xcode "
"Settings panel."
msgstr ""
"iOS iOS Simulator "
" Xcode iOS "
"Simulator "
" Xcode Settings Platforms iOS Simulator "
""
#: ../../using/ios.rst:163
msgid "Adding Python to an iOS project"
msgstr "iOS Python "
#: ../../using/ios.rst:165
msgid ""
"Python can be added to any iOS project, using either Swift or Objective C. "
"The following examples will use Objective C; if you are using Swift, you may "
"find a library like `PythonKit `__ to "
"be helpful."
msgstr ""
"Python Swift Objective-C iOS "
" Objective-C Swift "
" `PythonKit `__ "
""
#: ../../using/ios.rst:170
msgid "To add Python to an iOS Xcode project:"
msgstr "Python iOS Xcode :"
msgid ""
"Build or obtain a Python ``XCFramework``. See the instructions in :source:"
"`Platforms/Apple/iOS/README.md` (in the CPython source distribution) for "
"details on how to build a Python ``XCFramework``. At a minimum, you will "
"need a build that supports ``arm64-apple-ios``, plus one of either ``arm64-"
"apple-ios-simulator`` or ``x86_64-apple-ios-simulator``."
msgstr ""
"Python ``XCFramework`` \n"
"Python ``XCFramework`` CPython "
" :source:`Platforms/Apple/iOS/README.md` \n"
"``arm64-apple-ios`` ``arm64-apple-ios-simulator`` "
"``x86_64-apple-ios-simulator`` "
#: ../../using/ios.rst:178
msgid ""
"Drag the ``XCframework`` into your iOS project. In the following "
"instructions, we'll assume you've dropped the ``XCframework`` into the root "
"of your project; however, you can use any other location that you want by "
"adjusting paths as needed."
msgstr ""
"``XCframework`` iOS "
" ``XCframework`` "
""
#: ../../using/ios.rst:183
msgid ""
"Add your application code as a folder in your Xcode project. In the "
"following instructions, we'll assume that your user code is in a folder "
"named ``app`` in the root of your project; you can use any other location by "
"adjusting paths as needed. Ensure that this folder is associated with your "
"app target."
msgstr ""
" Xcode "
" ``app`` "
""
""
""
msgid ""
"Select the app target by selecting the root node of your Xcode project, then "
"the target name in the sidebar that appears."
msgstr ""
"Xcode "
""
#: ../../using/ios.rst:192
msgid ""
"In the \"General\" settings, under \"Frameworks, Libraries and Embedded "
"Content\", add ``Python.xcframework``, with \"Embed & Sign\" selected."
msgstr ""
"\"General\" \"Frameworks, Libraries and Embedded Content\" "
"\"Embed & Sign\" ``Python.xcframework`` "
#: ../../using/ios.rst:195
msgid "In the \"Build Settings\" tab, modify the following:"
msgstr "\"Build Settings\" :"
#: ../../using/ios.rst:197
msgid "Build Options"
msgstr "Build Options"
#: ../../using/ios.rst:199
msgid "User Script Sandboxing: No"
msgstr "User Script Sandboxing: No"
#: ../../using/ios.rst:200
msgid "Enable Testability: Yes"
msgstr "Enable Testability: Yes"
#: ../../using/ios.rst:202
msgid "Search Paths"
msgstr "Search Paths"
#: ../../using/ios.rst:204
msgid "Framework Search Paths: ``$(PROJECT_DIR)``"
msgstr "Framework Search Paths: ``$(PROJECT_DIR)``"
#: ../../using/ios.rst:205
msgid ""
"Header Search Paths: ``\"$(BUILT_PRODUCTS_DIR)/Python.framework/Headers\"``"
msgstr ""
"Header Search Paths: ``\"$(BUILT_PRODUCTS_DIR)/Python.framework/Headers\"``"
#: ../../using/ios.rst:207
msgid "Apple Clang - Warnings - All languages"
msgstr "Apple Clang - Warnings - All languages"
#: ../../using/ios.rst:209
msgid "Quoted Include In Framework Header: No"
msgstr "Quoted Include In Framework Header: No"
msgid ""
"Add a build step that processes the Python standard library, and your own "
"Python binary dependencies. In the \"Build Phases\" tab, add a new \"Run "
"Script\" build step *before* the \"Embed Frameworks\" step, but *after* the "
"\"Copy Bundle Resources\" step. Name the step \"Process Python libraries\", "
"disable the \"Based on dependency analysis\" checkbox, and set the script "
"content to:"
msgstr ""
"Python Python "
"\n"
"\"Build Phases\" \"Embed Frameworks\" ** \"Copy "
"Bundle Resources\" ** \"Run Script\" "
"\n"
" \"Process Python libraries\" \"Based on "
"dependency analysis\" "
":"
#: ../../using/ios.rst:218
msgid ""
"set -e\n"
"source $PROJECT_DIR/Python.xcframework/build/build_utils.sh\n"
"install_python Python.xcframework app"
msgstr ""
"set -e\n"
"source $PROJECT_DIR/Python.xcframework/build/build_utils.sh\n"
"install_python Python.xcframework app"
#: ../../using/ios.rst:224
msgid ""
"If you have placed your XCframework somewhere other than the root of your "
"project, modify the path to the first argument."
msgstr ""
" XCFramework "
""
#: ../../using/ios.rst:227
msgid ""
"Add Objective C code to initialize and use a Python interpreter in embedded "
"mode. You should ensure that:"
msgstr ""
"Python Objective C "
":"
#: ../../using/ios.rst:230
msgid "UTF-8 mode (:c:member:`PyPreConfig.utf8_mode`) is *enabled*;"
msgstr ""
"UTF-8 (:c:member:`PyPreConfig.utf8_mode`) ** "
#: ../../using/ios.rst:231
msgid "Buffered stdio (:c:member:`PyConfig.buffered_stdio`) is *disabled*;"
msgstr ""
"Buffered stdio (:c:member:`PyConfig.buffered_stdio`) ** "
""
#: ../../using/ios.rst:232
msgid "Writing bytecode (:c:member:`PyConfig.write_bytecode`) is *disabled*;"
msgstr ""
" (:c:member:`PyConfig.write_bytecode`) ** "
""
#: ../../using/ios.rst:233
msgid ""
"Signal handlers (:c:member:`PyConfig.install_signal_handlers`) are *enabled*;"
msgstr ""
" (:c:member:`PyConfig.install_signal_handlers`) ** "
""
#: ../../using/ios.rst:234
msgid ""
"System logging (:c:member:`PyConfig.use_system_logger`) is *enabled* "
"(optional, but strongly recommended; this is enabled by default);"
msgstr ""
" (:c:member:`PyConfig.use_system_logger`) ** "
" ()"
#: ../../using/ios.rst:236
msgid ""
":envvar:`PYTHONHOME` for the interpreter is configured to point at the "
"``python`` subfolder of your app's bundle; and"
msgstr ""
" :envvar:`PYTHONHOME` ``python`` "
""
#: ../../using/ios.rst:238
msgid "The :envvar:`PYTHONPATH` for the interpreter includes:"
msgstr " :envvar:`PYTHONPATH` "
#: ../../using/ios.rst:240
msgid "the ``python/lib/python3.X`` subfolder of your app's bundle,"
msgstr " ``python/lib/python3.X`` "
#: ../../using/ios.rst:241
msgid ""
"the ``python/lib/python3.X/lib-dynload`` subfolder of your app's bundle, and"
msgstr " ``python/lib/python3.X/lib-dynload`` "
#: ../../using/ios.rst:242
msgid "the ``app`` subfolder of your app's bundle"
msgstr " ``app`` "
#: ../../using/ios.rst:244
msgid ""
"Your app's bundle location can be determined using ``[[NSBundle mainBundle] "
"resourcePath]``."
msgstr ""
" ``[[NSBundle mainBundle] resourcePath]`` "
""
#: ../../using/ios.rst:247
msgid ""
"Steps 7 and 8 of these instructions assume that you have a single folder of "
"pure Python application code, named ``app``. If you have third-party binary "
"modules in your app, some additional steps will be required:"
msgstr ""
" 7, 8 ``app`` Python "
""
":"
#: ../../using/ios.rst:251
msgid ""
"You need to ensure that any folders containing third-party binaries are "
"either associated with the app target, or are explicitly copied as part of "
"step 7. Step 7 should also purge any binaries that are not appropriate for "
"the platform a specific build is targeting (i.e., delete any device binaries "
"if you're building an app targeting the simulator)."
msgstr ""
""
" 7 "
" 7 "
"("
")"
#: ../../using/ios.rst:257
msgid ""
"If you're using a separate folder for third-party packages, ensure that "
"folder is added to the end of the call to ``install_python`` in step 7, and "
"as part of the :envvar:`PYTHONPATH` configuration in step 8."
msgstr ""
" 7 "
" ``install_python`` 8 :envvar:"
"`PYTHONPATH` "
#: ../../using/ios.rst:261
msgid ""
"If any of the folders that contain third-party packages will contain ``."
"pth`` files, you should add that folder as a *site directory* (using :meth:"
"`site.addsitedir`), rather than adding to :envvar:`PYTHONPATH` or :attr:`sys."
"path` directly."
msgstr ""
" ``.pth`` :"
"envvar:`PYTHONPATH` :attr:`sys.path` "
"(:meth:`site.addsitedir` ) "
""
#: ../../using/ios.rst:267
msgid "Testing a Python package"
msgstr "Python "
msgid ""
"The CPython source tree contains :source:`a testbed project ` that is used to run the CPython test suite on the iOS simulator. "
"This testbed can also be used as a testbed project for running your Python "
"library's test suite on iOS."
msgstr ""
"CPython iOS CPython "
" :source:` ` "
"\n"
" Python iOS "
""
msgid ""
"After building or obtaining an iOS XCFramework (see :source:`Platforms/Apple/"
"iOS/README.md` for details), create a clone of the Python iOS testbed "
"project. If you used the ``Platforms/Apple`` build script to build the "
"XCframework, you can run:"
msgstr ""
"iOS XCFramework (:source:`Platforms/Apple/iOS/"
"README.md` )Python iOS "
"\n"
"``Platforms/Apple`` XCframework "
":"
#: ../../using/ios.rst:277
msgid ""
"$ python cross-build/iOS/testbed clone --app --app app-testbed"
msgstr ""
"$ python cross-build/iOS/testbed clone --app --app app-testbed"
#: ../../using/ios.rst:281
msgid "Or, if you've sourced your own XCframework, by running:"
msgstr ""
" XCFramework "
":"
msgid ""
"$ python Platforms/Apple/testbed clone --platform iOS --framework --app --app app-"
"testbed"
msgstr ""
"$ python Platforms/Apple/testbed clone --platform iOS --framework --app --app app-"
"testbed"
#: ../../using/ios.rst:287
msgid ""
"Any folders specified with the ``--app`` flag will be copied into the cloned "
"testbed project. The resulting testbed will be created in the ``app-"
"testbed`` folder. In this example, the ``module1`` and ``module2`` would be "
"importable modules at runtime. If your project has additional dependencies, "
"they can be installed into the ``app-testbed/Testbed/app_packages`` folder "
"(using ``pip install --target app-testbed/Testbed/app_packages`` or similar)."
msgstr ""
"``--app`` "
" ``app-testbed`` "
" ``module1`` ``module2`` "
" "
"(``pip install --target app-testbed/Testbed/app_packages`` ) "
" ``app-testbed/Testbed/app_packages`` "
""
msgid ""
"You can then use the ``app-testbed`` folder to run the test suite for your "
"app, For example, if ``module1.tests`` was the entry point to your test "
"suite, you could run:"
msgstr ""
"``app-testbed`` "
"\n"
" ``module1.tests`` "
":"
#: ../../using/ios.rst:298
msgid "$ python app-testbed run -- module1.tests"
msgstr "$ python app-testbed run -- module1.tests"
msgid ""
"This is the equivalent of running ``python -m module1.tests`` on a desktop "
"Python build. Any arguments after the ``--`` will be passed to the testbed "
"as if they were arguments to ``python -m`` on a desktop machine."
msgstr ""
" Python ``python -m module1.tests`` "
"\n"
"``--`` ``python -m`` "
""
msgid "You can also open the testbed project in Xcode by running:"
msgstr ""
" Xcode "
":"
#: ../../using/ios.rst:308
msgid "$ open app-testbed/iOSTestbed.xcodeproj"
msgstr "$ open app-testbed/iOSTestbed.xcodeproj"
msgid "This will allow you to use the full Xcode suite of tools for debugging."
msgstr " Xcode "
msgid ""
"The arguments used to run the test suite are defined as part of the test "
"plan. To modify the test plan, select the test plan node of the project tree "
"(it should be the first child of the root node), and select the "
"\"Configurations\" tab. Modify the \"Arguments Passed On Launch\" value to "
"change the testing arguments."
msgstr ""
""
"\n"
" ("
") \"Configurations\" "
"\n"
"\"Arguments Passed On Launch\" "
msgid ""
"The test plan also disables parallel testing, and specifies the use of the "
"``Testbed.lldbinit`` file for providing configuration of the debugger. The "
"default debugger configuration disables automatic breakpoints on the "
"``SIGINT``, ``SIGUSR1``, ``SIGUSR2``, and ``SIGXFSZ`` signals."
msgstr ""
" ``Testbed.lldbinit`` "
"\n"
"``SIGINT````SIGUSR1````SIGUSR2``"
"``SIGXFSZ`` "
#: ../../using/ios.rst:326
msgid "App Store Compliance"
msgstr "App Store "
msgid ""
"The only mechanism for distributing apps to third-party iOS devices is to "
"submit the app to the iOS App Store; apps submitted for distribution must "
"pass Apple's app review process. This process includes a set of automated "
"validation rules that inspect the submitted application bundle for "
"problematic code. There are some steps that must be taken to ensure that "
"your app will be able to pass these validation steps."
msgstr ""
" iOS iOS App Store "
"\n"
"Apple \n"
""
"\n"
""
""
#: ../../using/ios.rst:336
msgid "Incompatible code in the standard library"
msgstr ""
#: ../../using/ios.rst:338
msgid ""
"The Python standard library contains some code that is known to violate "
"these automated rules. While these violations appear to be false positives, "
"Apple's review rules cannot be challenged; so, it is necessary to modify the "
"Python standard library for an app to pass App Store review."
msgstr ""
"Python "
" "
"Apple Python "
" App Store "
#: ../../using/ios.rst:343
msgid ""
"The Python source tree contains :source:`a patch file ` that will remove all code that is known to cause "
"issues with the App Store review process. This patch is applied "
"automatically when building for iOS."
msgstr ""
"Python App Store "
" :source:` ` iOS "
""
#: ../../using/ios.rst:349
msgid "Privacy manifests"
msgstr ""
msgid ""
"In April 2025, Apple introduced a requirement for `certain third-party "
"libraries to provide a Privacy Manifest `__. As a result, if you have a binary module "
"that uses one of the affected libraries, you must provide an ``.xcprivacy`` "
"file for that library. OpenSSL is one library affected by this requirement, "
"but there are others."
msgstr ""
"2025 4 Apple `"
" `__\n"
""
" ``.xcprivacy`` \n"
"OpenSSL "
""
msgid ""
"If you produce a binary module named ``mymodule.so``, and use you the Xcode "
"build script described in step 7 above, you can place a ``mymodule."
"xcprivacy`` file next to ``mymodule.so``, and the privacy manifest will be "
"installed into the required location when the binary module is converted "
"into a framework."
msgstr ""
"``mymodule.so`` 7 "
" Xcode ``mymodule.so`` "
"``mymodule.xcprivacy`` \n"
""
""