From d6c6e8f6b77e341cabe64e286a374856763aa665 Mon Sep 17 00:00:00 2001
From: Tom Pollard <tpollard@mit.edu>
Date: Fri, 14 Jun 2024 23:05:45 -0400
Subject: [PATCH] Replace setup.py with pyproject.toml

---
 setup.py | 94 --------------------------------------------------------
 1 file changed, 94 deletions(-)
 delete mode 100644 setup.py

diff --git a/setup.py b/setup.py
deleted file mode 100644
index 8df9dfd..0000000
--- a/setup.py
+++ /dev/null
@@ -1,94 +0,0 @@
-# Always prefer setuptools over distutils
-from setuptools import setup
-from pathlib import Path
-
-# To use a consistent encoding
-from os import path
-
-here = path.abspath(path.dirname(__file__))
-
-# Get the long description from the README file
-this_directory = Path(__file__).parent
-long_description = (this_directory / "README.md").read_text()
-
-setup(
-    name='tableone',
-
-    # Versions should comply with PEP440. 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='0.9.0',
-
-    description='TableOne',
-    long_description=long_description,
-    long_description_content_type='text/markdown',
-
-    # The project's main homepage.
-    url='https://github.com/tompollard/tableone',
-
-    # Author details
-    author='Tom Pollard',
-    author_email='tpollard@mit.edu',
-
-    # Choose your license
-    license='MIT',
-
-    # What does your project relate to?
-    keywords='Table one Table 1 clinical research population cohort',
-
-    # 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']),
-    packages=['tableone'],
-
-    # Alternatively, if you want to distribute just a my_module.py, uncomment
-    # this:
-    # py_modules=['tableone', 'modality'],
-
-    # 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/requirements.html
-    install_requires=[
-        'numpy>=1.19.1',
-        'pandas>=2.0.3',
-        'scipy>=1.10.1',
-        'statsmodels>=0.14.1',
-        'tabulate>=0.9.0',
-        'Jinja2==3.1.4',
-        'openpyxl==3.1.2'
-        ],
-
-    # 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={'wfdb': ['wfdb.config'],
-    # },
-    include_package_data=True,
-
-    # 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 # noqa
-    # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
-    # data_files=[('my_data', ['data/data_file'])],
-    # data_files=[('config', ['wfdb.config'])],
-
-    # 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',
-    #     ],
-    # },
-
-)