|
| 1 | +import os |
| 2 | +import sys |
| 3 | +import pathlib |
| 4 | +from setuptools import setup |
| 5 | + |
| 6 | +ORG = "intel" |
| 7 | +NAME = "project-example-for-python" |
| 8 | +DESCRIPTION = "A short desciption of your project" |
| 9 | +VERSION = "1.33.7" |
| 10 | +AUTHOR_NAME = "You Name Here!" |
| 11 | +AUTHOR_EMAIL = "some.body@once.toldme" |
| 12 | + |
| 13 | +SELF_PATH = os.path.dirname(os.path.abspath(__file__)) |
| 14 | + |
| 15 | +README = pathlib.Path(SELF_PATH, "README.md").read_text() |
| 16 | + |
| 17 | +# Folders on disk for Python packages must be _ and not - |
| 18 | +IMPORT_NAME = NAME.replace("-", "_") |
| 19 | + |
| 20 | +setup( |
| 21 | + name=NAME, |
| 22 | + version=VERSION, |
| 23 | + description=DESCRIPTION, |
| 24 | + long_description=README, |
| 25 | + # long_description_content_type is needed to make non-rst readmes display |
| 26 | + # correctly in PyPi, if you see a warning saying something like "I don't |
| 27 | + # know what this means" don't listen to it, it lies, it does know what this |
| 28 | + # means and if you have a .md README then you need to keep this line. |
| 29 | + long_description_content_type="text/markdown", |
| 30 | + author=AUTHOR_NAME, |
| 31 | + author_email=AUTHOR_EMAIL, |
| 32 | + url='https://github.com/{}/{}'.format(ORG, NAME), |
| 33 | + license='MIT', |
| 34 | + |
| 35 | + keywords=[ |
| 36 | + 'this', |
| 37 | + 'is', |
| 38 | + 'where', |
| 39 | + 'searchable', |
| 40 | + 'keywords', |
| 41 | + 'go', |
| 42 | + ], |
| 43 | + |
| 44 | + # Your package will fail to upload if you don't abide by these dude!: |
| 45 | + # https://pypi.org/classifiers/ |
| 46 | + classifiers=[ |
| 47 | + 'Development Status :: 4 - Beta', |
| 48 | + 'Intended Audience :: Developers', |
| 49 | + 'License :: OSI Approved :: MIT License', |
| 50 | + 'License :: OSI Approved :: Apache Software License', |
| 51 | + 'Natural Language :: English', |
| 52 | + 'Operating System :: OS Independent', |
| 53 | + # You must list all the version of Python that you want to allow to |
| 54 | + # download your package here. If you don't list it, users trying to pip |
| 55 | + # install it won't be able to get it from PyPi |
| 56 | + 'Programming Language :: Python :: 3.6', |
| 57 | + 'Programming Language :: Python :: 3.7', |
| 58 | + 'Programming Language :: Python :: 3.8', |
| 59 | + 'Programming Language :: Python :: Implementation :: CPython', |
| 60 | + 'Programming Language :: Python :: Implementation :: PyPy', |
| 61 | + ], |
| 62 | + |
| 63 | + # Dependencies got here aka install_requires=['dffml'] |
| 64 | + install_requires=[], |
| 65 | + # Dependencies only needed for running your tests go here |
| 66 | + tests_require=[], |
| 67 | + # If you include data files in your repo, you probably want the following |
| 68 | + # two lines |
| 69 | + include_package_data=True, |
| 70 | + zip_safe=False, |
| 71 | + # Install development dependencies with |
| 72 | + # pip install folder_containing_this_setup_py[dev] |
| 73 | + extras_require={ |
| 74 | + "dev": [ |
| 75 | + "coverage", |
| 76 | + "codecov", |
| 77 | + "sphinx", |
| 78 | + "sphinxcontrib-asyncio", |
| 79 | + "black", |
| 80 | + "sphinx_rtd_theme", |
| 81 | + ], |
| 82 | + }, |
| 83 | + # Python's plugin system, console_scripts says make command line utilities |
| 84 | + # out of these functions, note the `python.path : obj_in_file` syntax. |
| 85 | + # Don't forget the `:`! |
| 86 | + entry_points={ |
| 87 | + 'console_scripts': [ |
| 88 | + 'script = {}.cli:SCRIPT'.format(IMPORT_NAME), |
| 89 | + 'scriptscript = {}.cli_again:SCRIPTSCRIPT'.format(IMPORT_NAME), |
| 90 | + 'ufb = {}.cli:import_SCRIPT'.format(IMPORT_NAME), |
| 91 | + ], |
| 92 | + }, |
| 93 | +) |
0 commit comments