Giter Club home page Giter Club logo

Comments (2)

PhilParisi avatar PhilParisi commented on September 17, 2024

Note, I just updated my Microsoft Visual C++ after seeing that in the error message (I think I installed the correct module...). Similar errors still persist in the install. See below output:

(aliaa) C:\Users\Phillip\Documents\VirtualEnvironments>pip install git+https://github.com/aburrell/aacgmv2.git
Collecting git+https://github.com/aburrell/aacgmv2.git
Cloning https://github.com/aburrell/aacgmv2.git to c:\users\phillip\appdata\local\temp\pip-req-build-ehws3wg1
Running command git clone --filter=blob:none --quiet https://github.com/aburrell/aacgmv2.git 'C:\Users\Phillip\AppData\Local\Temp\pip-req-build-ehws3wg1'
Resolved https://github.com/aburrell/aacgmv2.git to commit ab78335
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: numpy in c:\users\phillip\documents\virtualenvironments\aliaa\lib\site-packages (from aacgmv2==2.6.3) (1.25.1)
Building wheels for collected packages: aacgmv2
Building wheel for aacgmv2 (pyproject.toml) ... error
error: subprocess-exited-with-error

× Building wheel for aacgmv2 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [311 lines of output]
C:\Users\Phillip\AppData\Local\Temp\pip-build-env-scgsdspt\overlay\Lib\site-packages\setuptools\config_apply_pyprojecttoml.py:69: SetuptoolsWarning: install_requires overwritten in pyproject.toml (dependencies)
corresp(dist, value, root_dir)
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-39
creating build\lib.win-amd64-cpython-39\aacgmv2
copying aacgmv2\deprecated.py -> build\lib.win-amd64-cpython-39\aacgmv2
copying aacgmv2\utils.py -> build\lib.win-amd64-cpython-39\aacgmv2
copying aacgmv2\wrapper.py -> build\lib.win-amd64-cpython-39\aacgmv2
copying aacgmv2_init_.py -> build\lib.win-amd64-cpython-39\aacgmv2
copying aacgmv2_main_.py -> build\lib.win-amd64-cpython-39\aacgmv2
running egg_info
writing aacgmv2.egg-info\PKG-INFO
writing dependency_links to aacgmv2.egg-info\dependency_links.txt
writing requirements to aacgmv2.egg-info\requires.txt
writing top-level names to aacgmv2.egg-info\top_level.txt
reading manifest file 'aacgmv2.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '.py[cod]' found anywhere in distribution
warning: no previously-included files matching 'pycache' found anywhere in distribution
warning: no previously-included files matching '
.so' found anywhere in distribution
warning: no previously-included files matching '.dylib' found anywhere in distribution
warning: no previously-included files matching '
.dSYM' found anywhere in distribution
warning: no previously-included files matching '.pytest_cache' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE-AstAlg.txt'
adding license file 'AUTHORS.rst'
writing manifest file 'aacgmv2.egg-info\SOURCES.txt'
C:\Users\Phillip\AppData\Local\Temp\pip-build-env-scgsdspt\overlay\Lib\site-packages\setuptools\command\build_py.py:201: _Warning: Package 'aacgmv2.aacgm_coeffs' is absent from the packages configuration.
!!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'aacgmv2.aacgm_coeffs' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'aacgmv2.aacgm_coeffs' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'aacgmv2.aacgm_coeffs' to be distributed and are
          already explicitly excluding 'aacgmv2.aacgm_coeffs' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  C:\Users\Phillip\AppData\Local\Temp\pip-build-env-scgsdspt\overlay\Lib\site-packages\setuptools\command\build_py.py:201: _Warning: Package 'aacgmv2.tests' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'aacgmv2.tests' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'aacgmv2.tests' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'aacgmv2.tests' to be distributed and are
          already explicitly excluding 'aacgmv2.tests' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  C:\Users\Phillip\AppData\Local\Temp\pip-build-env-scgsdspt\overlay\Lib\site-packages\setuptools\command\build_py.py:201: _Warning: Package 'aacgmv2.tests.environ' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'aacgmv2.tests.environ' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'aacgmv2.tests.environ' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'aacgmv2.tests.environ' to be distributed and are
          already explicitly excluding 'aacgmv2.tests.environ' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  C:\Users\Phillip\AppData\Local\Temp\pip-build-env-scgsdspt\overlay\Lib\site-packages\setuptools\command\build_py.py:201: _Warning: Package 'aacgmv2.tests.test_data' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'aacgmv2.tests.test_data' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'aacgmv2.tests.test_data' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'aacgmv2.tests.test_data' to be distributed and are
          already explicitly excluding 'aacgmv2.tests.test_data' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  copying aacgmv2\aacgmv2module.c -> build\lib.win-amd64-cpython-39\aacgmv2
  copying aacgmv2\igrf13coeffs.txt -> build\lib.win-amd64-cpython-39\aacgmv2
  copying aacgmv2\magmodel_1590-2020.txt -> build\lib.win-amd64-cpython-39\aacgmv2
  creating build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1590.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1595.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1600.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1605.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1610.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1615.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1620.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1625.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1630.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1635.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1640.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1645.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1650.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1655.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1660.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1665.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1670.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1675.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1680.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1685.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1690.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1695.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1700.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1705.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1710.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1715.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1720.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1725.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1730.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1735.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1740.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1745.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1750.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1755.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1760.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1765.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1770.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1775.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1780.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1785.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1790.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1795.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1800.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1805.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1810.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1815.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1820.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1825.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1830.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1835.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1840.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1845.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1850.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1855.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1860.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1865.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1870.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1875.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1880.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1885.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1890.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1895.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1900.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1905.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1910.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1915.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1920.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1925.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1930.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1935.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1940.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1945.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1950.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1955.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1960.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1965.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1970.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1975.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1980.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1985.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1990.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-1995.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-2000.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-2005.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-2010.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-2015.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-2020.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  copying aacgmv2\aacgm_coeffs\aacgm_coeffs-13-2025.asc -> build\lib.win-amd64-cpython-39\aacgmv2\aacgm_coeffs
  creating build\lib.win-amd64-cpython-39\aacgmv2\tests
  copying aacgmv2\tests\test_c_aacgmv2.py -> build\lib.win-amd64-cpython-39\aacgmv2\tests
  copying aacgmv2\tests\test_cmd_aacgmv2.py -> build\lib.win-amd64-cpython-39\aacgmv2\tests
  copying aacgmv2\tests\test_dep_aacgmv2.py -> build\lib.win-amd64-cpython-39\aacgmv2\tests
  copying aacgmv2\tests\test_py_aacgmv2.py -> build\lib.win-amd64-cpython-39\aacgmv2\tests
  copying aacgmv2\tests\test_struct_aacgmv2.py -> build\lib.win-amd64-cpython-39\aacgmv2\tests
  copying aacgmv2\tests\test_utils_aacgmv2.py -> build\lib.win-amd64-cpython-39\aacgmv2\tests
  creating build\lib.win-amd64-cpython-39\aacgmv2\tests\environ
  copying aacgmv2\tests\environ\test_environ_aacgmv2.py -> build\lib.win-amd64-cpython-39\aacgmv2\tests\environ
  creating build\lib.win-amd64-cpython-39\aacgmv2\tests\test_data
  copying aacgmv2\tests\test_data\test_convert.txt -> build\lib.win-amd64-cpython-39\aacgmv2\tests\test_data
  copying aacgmv2\tests\test_data\test_convert_mlt.txt -> build\lib.win-amd64-cpython-39\aacgmv2\tests\test_data
  copying aacgmv2\tests\test_data\test_convert_mlt_single_line.txt -> build\lib.win-amd64-cpython-39\aacgmv2\tests\test_data
  copying aacgmv2\tests\test_data\test_convert_single_line.txt -> build\lib.win-amd64-cpython-39\aacgmv2\tests\test_data
  running build_ext
  building 'aacgmv2._aacgmv2' extension
  creating build\temp.win-amd64-cpython-39
  creating build\temp.win-amd64-cpython-39\Release
  creating build\temp.win-amd64-cpython-39\Release\aacgmv2
  creating build\temp.win-amd64-cpython-39\Release\c_aacgmv2
  creating build\temp.win-amd64-cpython-39\Release\c_aacgmv2\src
  "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.36.32532\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -Ic_aacgmv2/include -IC:\Users\Phillip\Documents\VirtualEnvironments\aliaa\include -IC:\Users\Phillip\AppData\Local\Programs\Python\Python39\include -IC:\Users\Phillip\AppData\Local\Programs\Python\Python39\Include "-IC:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.36.32532\include" "-IC:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.36.32532\ATLMFC\include" "-IC:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\VS\include" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" /Tcaacgmv2/aacgmv2module.c /Fobuild\temp.win-amd64-cpython-39\Release\aacgmv2/aacgmv2module.obj
  aacgmv2module.c
  aacgmv2/aacgmv2module.c(1): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
  error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\BuildTools\\VC\\Tools\\MSVC\\14.36.32532\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for aacgmv2
Failed to build aacgmv2
ERROR: Could not build wheels for aacgmv2, which is required to install pyproject.toml-based projects

(and sorry for the close and re-opening the issue, misclick on my end)

from aacgmv2.

aburrell avatar aburrell commented on September 17, 2024

You need to reinstall your c compiler after installing the updated my Microsoft Visual C++. Windows only works correctly if all the things are installed in the correct order. This has solved identical problems in the past, hopefully it will work here too.

from aacgmv2.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.