diff --git a/setup.py b/setup.py index ba8447ee81d580ec5b38f49d595fdd6d9202946f..54cc1176414fad6e4a03599d43a9bdfa5f88b8bc 100644 --- a/setup.py +++ b/setup.py @@ -42,8 +42,7 @@ setup( # 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='REST service for the validation of "xml" against a XML Schema', - # Optional + description='REST service for the validation of "xml" against a XML Schema', # Optional # This is an optional longer description of your project that represents # the body of text which users will see when they visit PyPI. @@ -75,7 +74,7 @@ setup( # This should be your name or the name of the organization which owns the # project. - author='PTB', # Optional + author='Rolf Niepraschk', # Optional # This should be a valid email address corresponding to the author listed # above. @@ -115,11 +114,11 @@ setup( # Note that this is a list of additional keywords, separated # by commas, to be used to assist searching for the distribution in a # larger catalog. - keywords='xml, xsd, development', # Optional + keywords='xml, xsd, dcc', # Optional # When your source code is in a subdirectory under the project root, e.g. # `src/`, it is necessary to specify the `package_dir` argument. - ###package_dir={'': 'src'}, # Optional + ### package_dir={'': 'src'}, # Optional # You can just specify package directories manually here if your project is # simple. Or you can use find_packages(). @@ -130,10 +129,12 @@ setup( # # py_modules=["my_module"], # + packages=find_packages(where='src'), # Required packages=find_packages(exclude=['bin', 'examples', 'include', 'Kritik', + 'Koch', 'templates' ]), @@ -149,11 +150,7 @@ setup( # # For an analysis of "install_requires" vs pip's requirements files see: # https://packaging.python.org/en/latest/requirements.html - install_requires=['flask', - 'flask-cors', - 'requests', - 'xmlschema' - ], + install_requires=['peppercorn'], # Optional # List additional groups of dependencies here (e.g. development # dependencies). Users will be able to install these using the "extras" @@ -163,23 +160,23 @@ setup( # # Similar to `install_requires` above, these must be valid existing # projects. - # extras_require={ # Optional + #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. - # package_data={ # Optional - # 'sample': ['package_data.dat'], - # }, + #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/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 + #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 @@ -188,11 +185,11 @@ setup( # # 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={ # Optional + 'console_scripts': [ + 'sample=sample:main', + ], + }, # List additional URLs that are relevant to your project as a dict. #