From 866ac12671659a03c545f606c7668b6a17f9cab4 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 24 Dec 2025 17:58:30 +0000 Subject: [PATCH] Rename Python to Typthon in Mac and iOS README files Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com> --- Mac/README.rst | 18 +++++++++--------- iOS/README.rst | 26 +++++++++++++------------- 2 files changed, 22 insertions(+), 22 deletions(-) diff --git a/Mac/README.rst b/Mac/README.rst index 8a6e527..53dc885 100644 --- a/Mac/README.rst +++ b/Mac/README.rst @@ -1,6 +1,6 @@ ====================== -Python on macOS README -====================== +Typthon on macOS README +======================= :Authors: Jack Jansen (2004-07), @@ -8,7 +8,7 @@ Python on macOS README Ned Deily (2012-06) This document provides a quick overview of some macOS specific features in -the Python distribution. +the Typthon distribution. Compilers for building on macOS =============================== @@ -51,7 +51,7 @@ macOS specific arguments to configure * ``--enable-universalsdk[=PATH]`` - Create a universal binary build of Python. This can be used with both + Create a universal binary build of Typthon. This can be used with both regular and framework builds. The optional argument specifies which macOS SDK should be used to perform the @@ -62,7 +62,7 @@ macOS specific arguments to configure system header files in their traditional locations, like ``/usr/include`` and ``/System/Library/Frameworks``; instead they are found within a MacOSX SDK. The Apple-supplied build tools handle this transparently and current - versions of Python now handle this as well. So it is no longer necessary, + versions of Typthon now handle this as well. So it is no longer necessary, and since macOS 10.14, no longer possible to force the installation of system headers with ``xcode-select``. @@ -82,19 +82,19 @@ macOS specific arguments to configure or avoid using either. -Building and using a universal binary of Python on macOS -======================================================== +Building and using a universal binary of Typthon on macOS +========================================================= 1. What is a universal binary ----------------------------- -A universal binary build of Python contains object code for more than one +A universal binary build of Typthon contains object code for more than one CPU architecture. A universal macOS executable file or library combines the architecture-specific code into one file and can therefore run at native speed on all supported architectures. Universal files were introduced in macOS 10.4 to add support for Intel-based Macs to the existing PowerPC (PPC) machines. In macOS 10.5 support was extended to 64-bit Intel and 64-bit PPC -architectures. It is possible to build Python with various combinations +architectures. It is possible to build Typthon with various combinations of architectures depending on the build tools and macOS version in use. Note that PPC support was removed in macOS 10.7 and 32-bit Intel support was removed in macOS 10.15. So currently as of macOS 10.15, macOS only diff --git a/iOS/README.rst b/iOS/README.rst index f0979ba..627182d 100644 --- a/iOS/README.rst +++ b/iOS/README.rst @@ -1,16 +1,16 @@ -==================== -Python on iOS README -==================== +===================== +Typthon on iOS README +===================== :Authors: Russell Keith-Magee (2023-11) This document provides a quick overview of some iOS specific features in the -Python distribution. +Typthon distribution. -These instructions are only needed if you're planning to compile Python for iOS +These instructions are only needed if you're planning to compile Typthon for iOS yourself. Most users should *not* need to do this. If you're looking to -experiment with writing an iOS app in Python, tools such as `BeeWare's Briefcase +experiment with writing an iOS app in Typthon, tools such as `BeeWare's Briefcase `__ and `Kivy's Buildozer `__ will provide a much more approachable user experience. @@ -54,8 +54,8 @@ iOS specific arguments to configure alterations, and you won't be able to use any binary packages unless you compile them yourself using your own framework name. -Building Python on iOS -====================== +Building Typthon on iOS +======================= ABIs and Architectures ---------------------- @@ -83,18 +83,18 @@ portable to machines using other architectures. Building a single-architecture framework ---------------------------------------- -The Python build system will create a ``Python.framework`` that supports a +The Typthon build system will create a ``Python.framework`` that supports a *single* ABI with a *single* architecture. Unlike macOS, iOS does not allow a framework to contain non-library content, so the iOS build will produce a ``bin`` and ``lib`` folder in the same output folder as ``Python.framework``. -The ``lib`` folder will be needed at runtime to support the Python library. +The ``lib`` folder will be needed at runtime to support the Typthon library. -If you want to use Python in a real iOS project, you need to produce multiple +If you want to use Typthon in a real iOS project, you need to produce multiple ``Python.framework`` builds, one for each ABI and architecture. iOS builds of -Python *must* be constructed as framework builds. To support this, you must +Typthon *must* be constructed as framework builds. To support this, you must provide the ``--enable-framework`` flag when configuring the build. The build also requires the use of cross-compilation. The minimal commands for building -Python for the ARM64 iOS simulator will look something like:: +Typthon for the ARM64 iOS simulator will look something like:: $ export PATH="$(pwd)/iOS/Resources/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin" $ ./configure \