text: from setuptools import setup, find_packages  # Always prefer setuptools over distutils
  from codecs import open  # To use a consistent encoding
  from os import path
  
  here = path.abspath(path.dirname(__file__))
  
  setup(
      name='common_etl',
  
      version='0.0.2',
  
      description='A sample Python project',
  
      # The project's main homepage.
      url='https://github.com/OpenAddressesUK/common-ETL',
  
      # Author details
      author='John Murray',
  
      # Choose your license
      license='MIT',
  
      # You can just specify the packages manually here if your project is
      # simple. Or you can use find_packages().
      packages=find_packages(exclude=['contrib', 'docs', 'tests*']),
  
      # List run-time dependencies here.  These will be installed by pip when your
      # project is installed. For an analysis of "install_requires" vs pip's
      # requirements files see:
      # https://packaging.python.org/en/latest/technical.html#install-requires-vs-requirements-files
      # install_requires=['peppercorn'],
  
      # List additional groups of dependencies here (e.g. development dependencies).
      # You can install these using the following syntax, for example:
      # $ pip install -e .[dev,test]
      # extras_require = {
      #     '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 less, then these
      # have to be included in MANIFEST.in as well.
      # package_data={
      #     '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'])],
  
      # 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.
      # entry_points={
      #     'console_scripts': [
      #         'sample=sample:main',
      #     ],
      # },
  )
  