FazBrowse GitHub Viewer
|
Trending
|
URL:
|
Home
Tools:
[Download Repo ZIP]
[View Raw Code]
[Original HTTPS Page]
python-docs-de/using/ios.po at 4a468b6215ef3deb4de67edbc3a6cd33f22860d4 · python/python-docs-de · GitHub
python
python-docs-de
Repository navigation
Code
Issues
Pull requests
2
(2)
Actions
Security and quality
Insights
Expand file tree
Breadcrumbs
python-docs-de
/
using
/
ios.po
Copy path
More file actions
More file actions
Latest commit
History
History
History
559 lines (472 loc) · 20.8 KB
Breadcrumbs
python-docs-de
/
using
/
ios.po
Copy path
File metadata and controls
559 lines (472 loc) · 20.8 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
#
SOME DESCRIPTIVE TITLE.
#
Copyright (C) 2001 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.14\n
"
"
Report-Msgid-Bugs-To
:
\n
"
"
POT-Creation-Date
:
2025-06-27 14:20+0000\n
"
"
PO-Revision-Date
:
2025-08-02 17:35+0000\n
"
"
Language-Team
:
German (https://app.transifex.com/python-doc/teams/5390/de/)\n
"
"
MIME-Version
:
1.0\n
"
"
Content-Type
:
text/plain; charset=UTF-8\n
"
"
Content-Transfer-Encoding
:
8bit\n
"
"
Language
:
de\n
"
"
Plural-Forms
:
nplurals=2; plural=(n != 1);\n
"
msgid
"Using Python on iOS"
msgstr
""
msgid
"Authors"
msgstr
""
msgid
"Russell Keith-Magee (2024-03)"
msgstr
""
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
""
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
""
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 <embedding>`. 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
""
msgid
""
"If you're looking to experiment for the first time with writing an iOS app "
"in Python, projects such as `BeeWare <https://beeware.org>`__ and `Kivy "
"<https://kivy.org>`__ 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
""
msgid
"Python at runtime on iOS"
msgstr
""
msgid
"iOS version compatibility"
msgstr
""
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
""
msgid
"Platform identification"
msgstr
""
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
""
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
""
msgid
""
":func:`os.uname` reports kernel-level details; it will report a name of "
"``Darwin``."
msgstr
""
msgid
"Standard library availability"
msgstr
""
msgid
""
"The Python standard library has some notable omissions and restrictions on "
"iOS. See the :ref:`API availability guide for iOS <mobile-availability>` for "
"details."
msgstr
""
msgid
"Binary extension modules"
msgstr
""
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
""
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
""
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 <adding-ios>`."
msgstr
""
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
""
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
""
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
""
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
""
msgid
""
"The output of ``xcrun`` includes paths that are machine specific, resulting "
"in a sysconfig module that cannot be shared between users; and"
msgstr
""
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
""
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
""
msgid
"Installing Python on iOS"
msgstr
""
msgid
"Tools for building iOS apps"
msgstr
""
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
""
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
""
msgid
"Adding Python to an iOS project"
msgstr
""
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 <https://github.com/pvieito/PythonKit>`__ to "
"be helpful."
msgstr
""
msgid
"To add Python to an iOS Xcode project:"
msgstr
""
msgid
""
"Build or obtain a Python ``XCFramework``. See the instructions in :source:"
"`iOS/README.rst` (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
""
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
""
msgid
""
"Drag the ``iOS/Resources/dylib-Info-template.plist`` file into your project, "
"and ensure it is associated with the app target."
msgstr
""
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
""
msgid
""
"Select the app target by selecting the root node of your Xcode project, then "
"the target name in the sidebar that appears."
msgstr
""
msgid
""
"In the
\"
General
\"
settings, under
\"
Frameworks, Libraries and Embedded "
"Content
\"
, add ``Python.xcframework``, with
\"
Embed & Sign
\"
selected."
msgstr
""
msgid
"In the
\"
Build Settings
\"
tab, modify the following:"
msgstr
""
msgid
"Build Options"
msgstr
""
msgid
"User Script Sandboxing: No"
msgstr
""
msgid
"Enable Testability: Yes"
msgstr
""
msgid
"Search Paths"
msgstr
""
msgid
"Framework Search Paths: ``$(PROJECT_DIR)``"
msgstr
""
msgid
""
"Header Search Paths: ``
\"
$(BUILT_PRODUCTS_DIR)/Python.framework/Headers
\"
``"
msgstr
""
msgid
"Apple Clang - Warnings - All languages"
msgstr
""
msgid
"Quoted Include In Framework Header: No"
msgstr
""
msgid
""
"Add a build step that copies the Python standard library into your app. 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
\"
Install Target Specific Python Standard Library
\"
, disable "
"the
\"
Based on dependency analysis
\"
checkbox, and set the script content to:"
msgstr
""
msgid
""
"set -e\n"
"\n"
"mkdir -p
\"
$CODESIGNING_FOLDER_PATH/python/lib
\"
\n"
"if [
\"
$EFFECTIVE_PLATFORM_NAME
\"
=
\"
-iphonesimulator
\"
]; then\n"
" echo
\"
Installing Python modules for iOS Simulator
\"
\n"
" rsync -au --delete
\"
$PROJECT_DIR/Python.xcframework/ios-arm64_x86_64-"
"simulator/lib/
\"
\"
$CODESIGNING_FOLDER_PATH/python/lib/
\"
\n"
"else\n"
" echo
\"
Installing Python modules for iOS Device
\"
\n"
" rsync -au --delete
\"
$PROJECT_DIR/Python.xcframework/ios-arm64/lib/
\"
"
"
\"
$CODESIGNING_FOLDER_PATH/python/lib/
\"
\n"
"fi"
msgstr
""
msgid
""
"Note that the name of the simulator
\"
slice
\"
in the XCframework may be "
"different, depending the CPU architectures your ``XCFramework`` supports."
msgstr
""
msgid
""
"Add a second build step that processes the binary extension modules in the "
"standard library into
\"
Framework
\"
format. Add a
\"
Run Script
\"
build step "
"*directly after* the one you added in step 8, named
\"
Prepare Python Binary "
"Modules
\"
. It should also have
\"
Based on dependency analysis
\"
unchecked, "
"with the following script content:"
msgstr
""
msgid
""
"set -e\n"
"\n"
"install_dylib () {\n"
" INSTALL_BASE=$1\n"
" FULL_EXT=$2\n"
"\n"
" # The name of the extension file\n"
" EXT=$(basename
\"
$FULL_EXT
\"
)\n"
" # The location of the extension file, relative to the bundle\n"
" RELATIVE_EXT=${FULL_EXT#$CODESIGNING_FOLDER_PATH/}\n"
" # The path to the extension file, relative to the install base\n"
" PYTHON_EXT=${RELATIVE_EXT/$INSTALL_BASE/}\n"
" # The full dotted name of the extension module, constructed from the "
"file path.\n"
" FULL_MODULE_NAME=$(echo $PYTHON_EXT | cut -d
\"
.
\"
-f 1 | tr
\"
/
\"
\"
."
"
\"
);\n"
" # A bundle identifier; not actually used, but required by Xcode "
"framework packaging\n"
" FRAMEWORK_BUNDLE_ID=$(echo $PRODUCT_BUNDLE_IDENTIFIER.$FULL_MODULE_NAME "
"| tr
\"
_
\"
\"
-
\"
)\n"
" # The name of the framework folder.\n"
" FRAMEWORK_FOLDER=
\"
Frameworks/$FULL_MODULE_NAME.framework
\"
\n"
"\n"
" # If the framework folder doesn't exist, create it.\n"
" if [ ! -d
\"
$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER
\"
]; then\n"
" echo
\"
Creating framework for $RELATIVE_EXT
\"
\n"
" mkdir -p
\"
$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER
\"
\n"
" cp
\"
$CODESIGNING_FOLDER_PATH/dylib-Info-template.plist
\"
"
"
\"
$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/Info.plist
\"
\n"
" plutil -replace CFBundleExecutable -string
\"
$FULL_MODULE_NAME
\"
"
"
\"
$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/Info.plist
\"
\n"
" plutil -replace CFBundleIdentifier -string
\"
$FRAMEWORK_BUNDLE_ID
\"
"
"
\"
$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/Info.plist
\"
\n"
" fi\n"
"\n"
" echo
\"
Installing binary for $FRAMEWORK_FOLDER/$FULL_MODULE_NAME
\"
\n"
" mv
\"
$FULL_EXT
\"
\"
$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/"
"$FULL_MODULE_NAME
\"
\n"
" # Create a placeholder .fwork file where the .so was\n"
" echo
\"
$FRAMEWORK_FOLDER/$FULL_MODULE_NAME
\"
> ${FULL_EXT%.so}.fwork\n"
" # Create a back reference to the .so file location in the framework\n"
" echo
\"
${RELATIVE_EXT%.so}.fwork
\"
>
\"
$CODESIGNING_FOLDER_PATH/"
"$FRAMEWORK_FOLDER/$FULL_MODULE_NAME.origin
\"
\n"
" }\n"
"\n"
" PYTHON_VER=$(ls -1
\"
$CODESIGNING_FOLDER_PATH/python/lib
\"
)\n"
" echo
\"
Install Python $PYTHON_VER standard library extension modules...
\"
\n"
" find
\"
$CODESIGNING_FOLDER_PATH/python/lib/$PYTHON_VER/lib-dynload
\"
-name "
"
\"
*.so
\"
| while read FULL_EXT; do\n"
" install_dylib python/lib/$PYTHON_VER/lib-dynload/
\"
$FULL_EXT
\"
\n"
" done\n"
"\n"
" # Clean up dylib template\n"
" rm -f
\"
$CODESIGNING_FOLDER_PATH/dylib-Info-template.plist
\"
\n"
"\n"
" echo
\"
Signing frameworks as $EXPANDED_CODE_SIGN_IDENTITY_NAME "
"($EXPANDED_CODE_SIGN_IDENTITY)...
\"
\n"
" find
\"
$CODESIGNING_FOLDER_PATH/Frameworks
\"
-name
\"
*.framework
\"
-exec /"
"usr/bin/codesign --force --sign
\"
$EXPANDED_CODE_SIGN_IDENTITY
\"
"
"${OTHER_CODE_SIGN_FLAGS:-} -o runtime --timestamp=none --preserve-"
"metadata=identifier,entitlements,flags --generate-entitlement-der
\"
{}
\"
\\
;"
msgstr
""
msgid
""
"Add Objective C code to initialize and use a Python interpreter in embedded "
"mode. You should ensure that:"
msgstr
""
msgid
"UTF-8 mode (:c:member:`PyPreConfig.utf8_mode`) is *enabled*;"
msgstr
""
msgid
"Buffered stdio (:c:member:`PyConfig.buffered_stdio`) is *disabled*;"
msgstr
""
msgid
"Writing bytecode (:c:member:`PyConfig.write_bytecode`) is *disabled*;"
msgstr
""
msgid
""
"Signal handlers (:c:member:`PyConfig.install_signal_handlers`) are *enabled*;"
msgstr
""
msgid
""
"System logging (:c:member:`PyConfig.use_system_logger`) is *enabled* "
"(optional, but strongly recommended; this is enabled by default);"
msgstr
""
msgid
""
":envvar:`PYTHONHOME` for the interpreter is configured to point at the "
"``python`` subfolder of your app's bundle; and"
msgstr
""
msgid
"The :envvar:`PYTHONPATH` for the interpreter includes:"
msgstr
""
msgid
"the ``python/lib/python3.X`` subfolder of your app's bundle,"
msgstr
""
msgid
""
"the ``python/lib/python3.X/lib-dynload`` subfolder of your app's bundle, and"
msgstr
""
msgid
"the ``app`` subfolder of your app's bundle"
msgstr
""
msgid
""
"Your app's bundle location can be determined using ``[[NSBundle mainBundle] "
"resourcePath]``."
msgstr
""
msgid
""
"Steps 8, 9 and 10 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
""
msgid
""
"You need to ensure that any folders containing third-party binaries are "
"either associated with the app target, or copied in as part of step 8. Step "
"8 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
""
msgid
""
"Any folders that contain third-party binaries must be processed into "
"framework form by step 9. The invocation of ``install_dylib`` that processes "
"the ``lib-dynload`` folder can be copied and adapted for this purpose."
msgstr
""
msgid
""
"If you're using a separate folder for third-party packages, ensure that "
"folder is included as part of the :envvar:`PYTHONPATH` configuration in step "
"10."
msgstr
""
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
""
msgid
"Testing a Python package"
msgstr
""
msgid
""
"The CPython source tree contains :source:`a testbed project <iOS/testbed>` "
"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
""
msgid
""
"After building or obtaining an iOS XCFramework (See :source:`iOS/README.rst` "
"for details), create a clone of the Python iOS testbed project by running:"
msgstr
""
msgid
""
"$ python iOS/testbed clone --framework <path/to/Python.xcframework> --app "
"<path/to/module1> --app <path/to/module2> app-testbed"
msgstr
""
msgid
""
"You will need to modify the ``iOS/testbed`` reference to point to that "
"directory in the CPython source tree; 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/iOSTestbed/app_packages`` folder (using ``pip install --target app-"
"testbed/iOSTestbed/app_packages`` or similar)."
msgstr
""
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
""
msgid
"$ python app-testbed run -- module1.tests"
msgstr
""
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
""
msgid
"You can also open the testbed project in Xcode by running:"
msgstr
""
msgid
"$ open app-testbed/iOSTestbed.xcodeproj"
msgstr
""
msgid
"This will allow you to use the full Xcode suite of tools for debugging."
msgstr
""
msgid
"App Store Compliance"
msgstr
""
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."
msgstr
""
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
""
msgid
""
"The Python source tree contains :source:`a patch file <Mac/Resources/app-"
"store-compliance.patch>` 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
""
Back
|
FazBrowse Home
|
New Git URL