sync with internal repo1 (commit 03cdc24)

Author: leofang

SECURITY.md

@@ -4,9 +4,9 @@ NVIDIA is dedicated to the security and trust of our software products and servi
 
 If you need to report a security issue, please use the appropriate contact points outlined below. **Please do not report security vulnerabilities through GitHub/GitLab.**
 
-## Reporting Potential Security Vulnerability in cuQuantum
+## Reporting Potential Security Vulnerability in nvmath-python
 
-To report a potential security vulnerability in cuQuantum:
+To report a potential security vulnerability in nvmath-python:
 - Web: [Security Vulnerability Submission Form](https://www.nvidia.com/object/submit-security-vulnerability.html)
 - E-Mail: [email protected]
    - We encourage you to use the following PGP key for secure email communication: [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key)

builder/__init__.py

@@ -2,37 +2,3 @@
 #
 # SPDX-License-Identifier: Apache-2.0
 
-# How does the build system for cuquantum-python work?
-#
-# - When building a wheel ("pip wheel", "pip install .", or "python setup.py
-#   bdist_wheel" (discouraged!)), we want to build against the cutensor &
-#   cuquantum wheels that would be installed to site-packages, so we need
-#   two things:
-#     1. make them the *build-time* dependencies
-#     2. set up linker flags to modify rpaths
-#
-# - For 1. we opt in to use PEP-517, as setup_requires is known to not work
-#   automatically for users. This is the "price" we pay (by design of
-#   PEP-517), as it creates a new, "isolated" environment (referred to as
-#   build isolation) to which all build-time dependencies that live on PyPI
-#   are installed. Another "price" (also by design) is in the non-editable
-#   mode (without the "-e" flag) it always builds a wheel for installation.
-#
-# - For 2. the solution is to create our own bdist_wheel (called first) and
-#   build_ext (called later) commands. The former would inform the latter
-#   whether we are building a wheel.
-#
-# - There is an escape hatch for 1. which is to set "--no-build-isolation".
-#   Then, users are expected to set CUQUANTUM_ROOT (or CUSTATEVEC_ROOT &
-#   CUTENSORNET_ROOT) and manage all build-time dependencies themselves.
-#   This, together with "-e", would not produce any wheel, which is the old
-#   behavior offered by the environment variable CUQUANTUM_IGNORE_SOLVER=1
-#   that we removed and no longer works.
-#
-# - In any case, the custom build_ext command is in use, which would compute
-#   the needed compiler flags (depending on it's building a wheel or not)
-#   and overwrite the incoming Extension instances.
-#
-# - In any case, the dependencies (on PyPI wheels) are set up by default,
-#   and "--no-deps" can be passed as usual to tell pip to ignore the
-#   *run-time* dependencies.