text: """A setuptools based setup module.
  See:
  https://packaging.python.org/en/latest/distributing.html
  https://github.com/pypa/sampleproject
  """
  
  # Always prefer setuptools over distutils
  import os
  import subprocess
  from setuptools import setup, find_packages
  
  # io.open is needed for projects that support Python 2.7
  # It ensures open() defaults to text mode with universal newlines,
  # and accepts an argument to specify the text encoding
  # Python 3 only projects can skip this import
  from io import open
  
  here = os.path.abspath(os.path.dirname(__file__))
  
  # Get the long description from the README file
  with open(os.path.join(here, 'README.md'), encoding='utf-8') as f:
      long_description = f.read()
  
  # get all the git tags from the cmd line that follow our versioning pattern
  git_tags = subprocess.Popen(['git', 'tag', '--list', 'v*[0-9]', '--sort=version:refname'], stdout=subprocess.PIPE)
  # get the most recent tag after it's been sorted 👆
  latest_git_tag = subprocess.Popen(['tail', '-1'], stdin=git_tags.stdout, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
  git_tags.stdout.close()
  latest_version = latest_git_tag.communicate()[0]
  
  # PEP 440 won't accept the v in front, so here we remove it, strip the new line and decode the byte stream
  VERSION_FROM_GIT_TAG = latest_version[1:].strip().decode("utf-8")
  
  with open((here / "requirements.txt"), encoding="utf-8") as f:
      install_requires = f.read().splitlines()
  # removes comments in the requirements file
  dependencies = [dependency for dependency in install_requires if (dependency[0] != "#")]
  
  setup(
      # This is the name of your project. The first time you publish this
      # package, this name will be registered for you. It will determine how
      # users can install this project, e.g.:
      #
      # $ pip install sampleproject
      #
      # And where it will live on PyPI: https://pypi.org/project/sampleproject/
      #
      # There are some restrictions on what makes a valid project name
      # specification here:
      # https://packaging.python.org/specifications/core-metadata/#name
      name='statistical-clear-sky',  # Required
  
      # Versions should comply with PEP 440:
      # https://www.python.org/dev/peps/pep-0440/
      #
      # For a discussion on single-sourcing the version across setup.py and the
      # project code, see
      # https://packaging.python.org/en/latest/single_source_version.html
      version=VERSION_FROM_GIT_TAG,
  
      # This is a one-line description or tagline of what your project does. This
      # corresponds to the "Summary" metadata field:
      # https://packaging.python.org/specifications/core-metadata/#summary
      description='Statistical estimation of a clear sky signal from PV system power data',  # Optional
  
      # This is an optional longer description of your project that represents
      # the body of text which users will see when they visit PyPI.
      #
      # Often, this is the same as your README, so you can just read it in from
      # that file directly (as we have already done above)
      #
      # This field corresponds to the "Description" metadata field:
      # https://packaging.python.org/specifications/core-metadata/#description-optional
      long_description=long_description,  # Optional
  
      # Denotes that our long_description is in Markdown; valid values are
      # text/plain, text/x-rst, and text/markdown
      #
      # Optional if long_description is written in reStructuredText (rst) but
      # required for plain-text or Markdown; if unspecified, "applications should
      # attempt to render [the long_description] as text/x-rst; charset=UTF-8 and
      # fall back to text/plain if it is not valid rst" (see link below)
      #
      # This field corresponds to the "Description-Content-Type" metadata field:
      # https://packaging.python.org/specifications/core-metadata/#description-content-type-optional
      long_description_content_type='text/markdown',  # Optional (see note above)
  
      # This should be a valid link to your project's main homepage.
      #
      # This field corresponds to the "Home-Page" metadata field:
      # https://packaging.python.org/specifications/core-metadata/#home-page-optional
      url='https://github.com/bmeyers/StatisticalClearSky',  # Optional
  
      # This should be your name or the name of the organization which owns the
      # project.
      author='SLAC National Accelerator Laboratory - Bennet Meyers',  # Optional
  
      # This should be a valid email address corresponding to the author listed
      # above.
      author_email='bennetm@stanford.edu',  # Optional
  
      # Classifiers help users find your project by categorizing it.
      #
      # For a list of valid classifiers, see https://pypi.org/classifiers/
      classifiers=[  # Optional
          # How mature is this project? Common values are
          #   3 - Alpha
          #   4 - Beta
          #   5 - Production/Stable
          'Development Status :: 3 - Alpha',
  
          # Indicate who your project is intended for
          'Intended Audience :: Science/Research',
          'Topic :: Scientific/Engineering',
  
          # Pick your license as you wish
          'License :: OSI Approved :: BSD License',
  
          # Specify the Python versions you support here. In particular, ensure
          # that you indicate whether you support Python 2, Python 3 or both.
          # These classifiers are *not* checked by 'pip install'. See instead
          # 'python_requires' below.
          #'Programming Language :: Python :: 2',
          #'Programming Language :: Python :: 2.7',
          'Programming Language :: Python :: 3',
          #'Programming Language :: Python :: 3.4',
          #'Programming Language :: Python :: 3.5',
          'Programming Language :: Python :: 3.6',
          'Programming Language :: Python :: 3.7',
      ],
  
      # This field adds keywords for your project which will appear on the
      # project page. What does your project relate to?
      #
      # Note that this is a string of words separated by whitespace, not a list.
      keywords='solar pv photovoltaic',  # Optional
  
      # You can just specify package directories manually here if your project is
      # simple. Or you can use find_packages().
      #
      # Alternatively, if you just want to distribute a single Python file, use
      # the `py_modules` argument instead as follows, which will expect a file
      # called `my_module.py` to exist:
      #
      #   py_modules=["my_module"],
      #
      packages=find_packages(exclude=['tests', 'contrib', 'docs', 'clearsky', 'dataviewer', 'notebooks']),  # Required
  
      # Specify which Python versions you support. In contrast to the
      # 'Programming Language' classifiers above, 'pip install' will check this
      # and refuse to install the project if the version does not match. If you
      # do not support Python 2, you can simplify this to '>=3.5' or similar, see
      # https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
      #python_requires='>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, <4',
      python_requires='>=3.6, <4',
  
      # This field lists other packages that your project depends on to run.
      # Any package you put here will be installed by pip when your project is
      # installed, so they must be valid existing projects.
      #
      # For an analysis of "install_requires" vs pip's requirements files see:
      # https://packaging.python.org/en/latest/requirements.html
      install_requires=dependencies,
      # List additional groups of dependencies here (e.g. development
      # dependencies). Users will be able to install these using the "extras"
      # syntax, for example:
      #
      #   $ pip install sampleproject[dev]
      #
      # Similar to `install_requires` above, these must be valid existing
      # projects.
      extras_require={  # Optional
          'dev': ['check-manifest'],
          'test': ['coverage'],
      },
  
      # If there are data files included in your packages that need to be
      # installed, specify them here.
      #
      # If using Python 2.6 or earlier, then these have to be included in
      # MANIFEST.in as well.
      #package_data={  # Optional
      #    'sample': ['package_data.dat'],
      #},
  
      # Although 'package_data' is the preferred approach, in some case you may
      # need to place data files outside of your packages. See:
      # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files
      #
      # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
      #data_files=[('my_data', ['data/data_file'])],  # Optional
  
      # To provide executable scripts, use entry points in preference to the
      # "scripts" keyword. Entry points provide cross-platform support and allow
      # `pip` to create the appropriate form of executable for the target
      # platform.
      #
      # For example, the following would provide a command called `sample` which
      # executes the function `main` from this package when invoked:
      #entry_points={  # Optional
      #    'console_scripts': [
      #        'sample=sample:main',
      #    ],
      #},
      entry_points={
         'console_scripts': [
             'statistical_clear_sky=statistical_clear_sky.command_line:main',
         ],
      },
  
      # List additional URLs that are relevant to your project as a dict.
      #
      # This field corresponds to the "Project-URL" metadata fields:
      # https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use
      #
      # Examples listed include a pattern for specifying where the package tracks
      # issues, where the source is hosted, where to say thanks to the package
      # maintainers, and where to support the project financially. The key is
      # what's used to render the link text on PyPI.
      project_urls={  # Optional
          'Bug Reports': 'https://github.com/bmeyers/StatisticalClearSky/issues',
      },
  )
  