mirror of
https://github.com/craigerl/aprsd.git
synced 2024-11-21 15:51:52 -05:00
176 lines
6.5 KiB
TOML
176 lines
6.5 KiB
TOML
[project]
|
|
|
|
# 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 = "aprsd"
|
|
description = "APRSd is a APRS-IS server that can be used to connect to APRS-IS and send and receive APRS packets."
|
|
|
|
# Specify which Python versions you support. In contrast to the
|
|
# 'Programming Language' classifiers in this file, 'pip install' will check this
|
|
# and refuse to install the project if the version does not match. See
|
|
# https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
|
|
requires-python = ">=3.8"
|
|
|
|
dynamic = ["version", "dependencies", "optional-dependencies"]
|
|
|
|
# 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.
|
|
#
|
|
# This field corresponds to the "Description" metadata field:
|
|
# https://packaging.python.org/specifications/core-metadata/#description-optional
|
|
readme = {file = "README.rst", content-type = "text/x-rst"}
|
|
|
|
|
|
# This is either text indicating the license for the distribution, or a file
|
|
# that contains the license.
|
|
# https://packaging.python.org/en/latest/specifications/core-metadata/#license
|
|
license = {file = "LICENSE"}
|
|
|
|
# This should be your name or the name of the organization who originally
|
|
# authored the project, and a valid email address corresponding to the name
|
|
# listed.
|
|
authors = [
|
|
{name = "Craig Lamparter", email = "craig@craiger.org"},
|
|
{name = "Walter A. Boring IV", email = "waboring@hemna.com"},
|
|
{name = "Emre Saglam", email = "emresaglam@gmail.com"},
|
|
{name = "Jason Martin", email= "jhmartin@toger.us"},
|
|
{name = "John", email="johng42@users.noreply.github.com"},
|
|
{name = "Martiros Shakhzadyan", email="vrzh@vrzh.net"},
|
|
{name = "Zoe Moore", email="zoenb@mailbox.org"},
|
|
{name = "ranguli", email="hello@joshmurphy.ca"},
|
|
]
|
|
|
|
# This should be your name or the names of the organization who currently
|
|
# maintains the project, and a valid email address corresponding to the name
|
|
# listed.
|
|
maintainers = [
|
|
{name = "Craig Lamparter", email = "craig@craiger.org"},
|
|
{name = "Walter A. Boring IV", email = "waboring@hemna.com"},
|
|
]
|
|
|
|
# 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 list of additional keywords, separated
|
|
# by commas, to be used to assist searching for the distribution in a
|
|
# larger catalog.
|
|
keywords = [
|
|
"aprs",
|
|
"aprs-is",
|
|
"aprsd",
|
|
"aprsd-server",
|
|
"aprsd-client",
|
|
"aprsd-socket",
|
|
"aprsd-socket-server",
|
|
"aprsd-socket-client",
|
|
]
|
|
|
|
# Classifiers help users find your project by categorizing it.
|
|
#
|
|
# For a list of valid classifiers, see https://pypi.org/classifiers/
|
|
classifiers = [
|
|
"Development Status :: 5 - Production/Stable",
|
|
"Environment :: Console",
|
|
"Intended Audience :: Developers",
|
|
"Intended Audience :: End Users/Desktop",
|
|
"Intended Audience :: Information Technology",
|
|
"Topic :: Communications :: Ham Radio",
|
|
"Topic :: Internet",
|
|
"Programming Language :: Python :: 3 :: Only",
|
|
"Programming Language :: Python :: 3",
|
|
"Programming Language :: Python :: 3.8",
|
|
"Programming Language :: Python :: 3.9",
|
|
"Programming Language :: Python :: 3.10",
|
|
"Programming Language :: Python :: 3.11",
|
|
]
|
|
|
|
# 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 this field vs pip's requirements files see:
|
|
# https://packaging.python.org/discussions/install-requires-vs-requirements/
|
|
[tool.setuptools.dynamic]
|
|
dependencies = {file = ["./requirements.txt"]}
|
|
optional-dependencies.dev = {file = ["./requirements-dev.txt"]}
|
|
|
|
# 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]
|
|
#
|
|
# Optional dependencies the project provides. These are commonly
|
|
# referred to as "extras". For a more extensive definition see:
|
|
# https://packaging.python.org/en/latest/specifications/dependency-specifiers/#extras
|
|
# [project.optional-dependencies]
|
|
|
|
# List URLs that are relevant to your project
|
|
#
|
|
# This field corresponds to the "Project-URL" and "Home-Page" metadata fields:
|
|
# https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use
|
|
# https://packaging.python.org/specifications/core-metadata/#home-page-optional
|
|
#
|
|
# 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]
|
|
"Homepage" = "https://github.com/craigerl/aprsd"
|
|
"Bug Reports" = "https://github.com/craigerl/aprsd/issues"
|
|
"Source" = "https://github.com/craigerl/aprsd"
|
|
|
|
# The following would provide a command line executable called `sample`
|
|
# which executes the function `main` from this package when invoked.
|
|
[project.scripts]
|
|
aprsd = "aprsd.main:main"
|
|
|
|
[project.entry-points."oslo.config.opts"]
|
|
"aprsd.conf" = "aprsd.conf.opts:list_opts"
|
|
|
|
[project.entry-points."oslo.config.opts.defaults"]
|
|
"aprsd.conf" = "aprsd.conf:set_lib_defaults"
|
|
|
|
# If you are using a different build backend, you will need to change this.
|
|
[tool.setuptools]
|
|
# If there are data files included in your packages that need to be
|
|
# installed, specify them here.
|
|
py-modules = ["aprsd"]
|
|
package-data = {"sample" = ["*.dat"]}
|
|
packages = ["aprsd"]
|
|
|
|
[build-system]
|
|
requires = [
|
|
"setuptools>=69.5.0",
|
|
"setuptools_scm>=0",
|
|
"wheel",
|
|
]
|
|
build-backend = "setuptools.build_meta"
|
|
|
|
[tool.isort]
|
|
force_sort_within_sections = true
|
|
multi_line_output = 4
|
|
line_length = 88
|
|
# Inform isort of paths to import names that should be considered part of the "First Party" group.
|
|
#src_paths = ["src/openstack_loadtest"]
|
|
skip_gitignore = true
|
|
# If you need to skip/exclude folders, consider using skip_glob as that will allow the
|
|
# isort defaults for skip to remain without the need to duplicate them.
|
|
|
|
[tool.coverage.run]
|
|
branch = true
|
|
|
|
[tool.setuptools_scm]
|