Minor tweaks to wheel instructions

Author: ReeceHumphreys

docs/source/Build/pipInstall.rst

@@ -3,22 +3,18 @@
 
 .. _pipInstall:
 
-Advanced: Building and Installing Pre-Compiled Basilisk Wheels
-==============================================================
+Advanced: Building Pre-Compiled Basilisk Wheels
+===============================================
 
-.. warning::
-
-    :beta:`Pip Wheel Support` This method of building Basilisk is currently a beta feature, and should only be attempted by advanced users
-    familiar with `Python packaging and distribution
-    <https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/>`_.
-    This method is not yet guaranteed to work on every platform, and there are still some annoyances
-    to iron out, but we appreciate any feedback you may have.
+The following instructions explain how to build wheels with Basilisk.
+While we distribute pre-compiled wheels already in :ref:`bskInstall`,
+you can also build them manually using the steps below. This is desirable if
+you want to use Python wheels but still need to enable custom build options
+or link against a custom external module location.
 
-    Most users should see :ref:`configureBuild` for documentation on the regular build process.
 
-
-Building and Installing with ``pip``
-------------------------------------
+Building Wheels and Installing with ``pip``
+-------------------------------------------
 
 .. note::
 
@@ -44,16 +40,10 @@ Build options (as passed to ``conanfile.py`` and described in :ref:`configureBui
     installations (``pip install -e .``) are not currently supported. Please follow the standard
     :ref:`configureBuild` process.
 
-After installing
 
 Building Basilisk ``wheel`` File
 --------------------------------
 
-On its own, there is no significant benefit to installing Basilisk in this way. However, supporting standard Python
-packaging tools means that Basilisk can now be built into a pre-compiled `"wheel" (.whl) file
-<https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#wheels>`_ that can be shared
-and installed on other compatible machines.
-
 Using ``pip``, the command below will generate a ``Basilisk-*.whl`` file in the current directory::
 
     pip wheel --no-deps -v .
@@ -100,29 +90,6 @@ The following command is used to both download the code and compile Basilisk wit
 
     pip install git+https://github.com/AVSLab/basilisk.git
 
-Wheel Compatibility
--------------------
-
-.. warning::
-
-    Wheel compatibility is currently being verified across Python versions and different platforms. So far,
-    some users have reported successfully installing the same wheel on different Ubuntu versions and with
-    different Python versions, but your mileage may vary.
-
-    If you choose to try this feature and run into and problems, please `raise an issue
-    <https://github.com/AVSLab/basilisk/issues>`_ for the Basilisk maintainers to investigate.
-
-When installed using a standard Python packaging tool such as ``pip``, Basilisk will automatically be
-built using the `Python Limited C API <https://docs.python.org/3/c-api/stable.html#limited-c-api>`_. The
-resulting wheel file will contain a set of compiled Python extension modules that, at least in theory, can be
-run using any compatible Python version (currently, any from Python 3.8 to 3.11).
-
-To maintain backwards compatibility, standard Basilisk installations via ``python conanfile.py`` are not
-compatible between different Python versions, as is stated in :ref:`customPython`. However, users can
-also forcibly build with the Python Limited C API by providing the ``--pyLimitedAPI`` flag::
-
-    python conanfile.py --pyLimitedAPI 0x030800f0
-
 
 For Maintainers: Overview of Implementation
 -------------------------------------------
@@ -140,23 +107,12 @@ specified in ``pyproject.toml``). The builder then invokes ``python conanfile.py
 environment. The main reasons for this setting was to maintain the current default behaviour of
 ``conanfile.py``-based installation.
 
-Editable installations (i.e. ``pip install -e .``) are not currently supported for two main reasons:
-
-1. ``pip install -e .`` is currently overridden to maintain the existing ``python conanfile.py`` behaviour.
-2. Due to the underlying CMake build system, editable installs with ``pip`` require setting the
-   ``--no-build-isolation`` option, which means that the user must manually install the build requirements.
-   Since these build requirements are installed automatically by the standard ``conanfile.py`` installation,
-   it is the recommended method for editable installations.
-
-Tools such as `cibuildwheel <https://cibuildwheel.pypa.io/en/stable/>`_ can be used to build wheels that are
-automatically compatible with a broad range of operating system versions. These pre-compiled wheels can then
-be shared publicly using tools like `twine <https://pypi.org/project/twine/>`_ to upload them to the
-`Python Package Index (PyPi) <https://pypi.org/>`_, allowing users to simply ``pip install Basilisk``. We
-expect that these tools will be added into the Basilisk Continuous Integration pipeline in the future.
-
-Further discussions and implementation details can be found in
-`Basilisk merge request #737 <https://github.com/AVSLab/basilisk/pull/737>`_.
+Editable installations (i.e. ``pip install -e .``) are are partially supported. Python code changes are reflected
+automatically with this flag, but C++ components are not automatically rebuilt.
 
+This limitation exists because editable mode still routes through ``python conanfile.py``, but skips C++ rebuilds
+once the initial build exists. This avoids long native rebuilds and preserves the Conan/CMake configuration.
+...
 
 .. rubric:: Footnotes