|
12 | 12 | here = pathlib.Path(__file__).parent.resolve()
|
13 | 13 |
|
14 | 14 | # Get the long description from the README file
|
15 |
| -long_description = (here / 'README.md').read_text(encoding='utf-8') |
| 15 | +long_description = (here / "README.md").read_text(encoding="utf-8") |
16 | 16 |
|
17 | 17 | # Arguments marked as "Required" below must be included for upload to PyPI.
|
18 | 18 | # Fields marked as "Optional" may be commented out.
|
|
29 | 29 | # There are some restrictions on what makes a valid project name
|
30 | 30 | # specification here:
|
31 | 31 | # https://packaging.python.org/specifications/core-metadata/#name
|
32 |
| - name='sampleproject', # Required |
33 |
| - |
| 32 | + name="sampleproject", # Required |
34 | 33 | # Versions should comply with PEP 440:
|
35 | 34 | # https://www.python.org/dev/peps/pep-0440/
|
36 | 35 | #
|
37 | 36 | # For a discussion on single-sourcing the version across setup.py and the
|
38 | 37 | # project code, see
|
39 | 38 | # https://packaging.python.org/guides/single-sourcing-package-version/
|
40 |
| - version='2.0.0', # Required |
41 |
| - |
| 39 | + version="2.0.0", # Required |
42 | 40 | # This is a one-line description or tagline of what your project does. This
|
43 | 41 | # corresponds to the "Summary" metadata field:
|
44 | 42 | # https://packaging.python.org/specifications/core-metadata/#summary
|
45 |
| - description='A sample Python project', # Optional |
46 |
| - |
| 43 | + description="A sample Python project", # Optional |
47 | 44 | # This is an optional longer description of your project that represents
|
48 | 45 | # the body of text which users will see when they visit PyPI.
|
49 | 46 | #
|
|
53 | 50 | # This field corresponds to the "Description" metadata field:
|
54 | 51 | # https://packaging.python.org/specifications/core-metadata/#description-optional
|
55 | 52 | long_description=long_description, # Optional
|
56 |
| - |
57 | 53 | # Denotes that our long_description is in Markdown; valid values are
|
58 | 54 | # text/plain, text/x-rst, and text/markdown
|
59 | 55 | #
|
|
64 | 60 | #
|
65 | 61 | # This field corresponds to the "Description-Content-Type" metadata field:
|
66 | 62 | # https://packaging.python.org/specifications/core-metadata/#description-content-type-optional
|
67 |
| - long_description_content_type='text/markdown', # Optional (see note above) |
68 |
| - |
| 63 | + long_description_content_type="text/markdown", # Optional (see note above) |
69 | 64 | # This should be a valid link to your project's main homepage.
|
70 | 65 | #
|
71 | 66 | # This field corresponds to the "Home-Page" metadata field:
|
72 | 67 | # https://packaging.python.org/specifications/core-metadata/#home-page-optional
|
73 |
| - url='https://github.com/pypa/sampleproject', # Optional |
74 |
| - |
| 68 | + url="https://github.com/pypa/sampleproject", # Optional |
75 | 69 | # This should be your name or the name of the organization which owns the
|
76 | 70 | # project.
|
77 |
| - author='A. Random Developer', # Optional |
78 |
| - |
| 71 | + author="A. Random Developer", # Optional |
79 | 72 | # This should be a valid email address corresponding to the author listed
|
80 | 73 | # above.
|
81 |
| - author_email='[email protected]', # Optional |
82 |
| - |
| 74 | + author_email="[email protected]", # Optional |
83 | 75 | # Classifiers help users find your project by categorizing it.
|
84 | 76 | #
|
85 | 77 | # For a list of valid classifiers, see https://pypi.org/classifiers/
|
|
88 | 80 | # 3 - Alpha
|
89 | 81 | # 4 - Beta
|
90 | 82 | # 5 - Production/Stable
|
91 |
| - 'Development Status :: 3 - Alpha', |
92 |
| - |
| 83 | + "Development Status :: 3 - Alpha", |
93 | 84 | # Indicate who your project is intended for
|
94 |
| - 'Intended Audience :: Developers', |
95 |
| - 'Topic :: Software Development :: Build Tools', |
96 |
| - |
| 85 | + "Intended Audience :: Developers", |
| 86 | + "Topic :: Software Development :: Build Tools", |
97 | 87 | # Pick your license as you wish
|
98 |
| - 'License :: OSI Approved :: MIT License', |
99 |
| - |
| 88 | + "License :: OSI Approved :: MIT License", |
100 | 89 | # Specify the Python versions you support here. In particular, ensure
|
101 | 90 | # that you indicate you support Python 3. These classifiers are *not*
|
102 | 91 | # checked by 'pip install'. See instead 'python_requires' below.
|
103 |
| - 'Programming Language :: Python :: 3', |
104 |
| - 'Programming Language :: Python :: 3.6', |
105 |
| - 'Programming Language :: Python :: 3.7', |
106 |
| - 'Programming Language :: Python :: 3.8', |
107 |
| - 'Programming Language :: Python :: 3.9', |
| 92 | + "Programming Language :: Python :: 3", |
| 93 | + "Programming Language :: Python :: 3.7", |
| 94 | + "Programming Language :: Python :: 3.8", |
| 95 | + "Programming Language :: Python :: 3.9", |
108 | 96 | "Programming Language :: Python :: 3.10",
|
109 |
| - 'Programming Language :: Python :: 3 :: Only', |
| 97 | + "Programming Language :: Python :: 3 :: Only", |
110 | 98 | ],
|
111 |
| - |
112 | 99 | # This field adds keywords for your project which will appear on the
|
113 | 100 | # project page. What does your project relate to?
|
114 | 101 | #
|
115 | 102 | # Note that this is a list of additional keywords, separated
|
116 | 103 | # by commas, to be used to assist searching for the distribution in a
|
117 | 104 | # larger catalog.
|
118 |
| - keywords='sample, setuptools, development', # Optional |
119 |
| - |
| 105 | + keywords="sample, setuptools, development", # Optional |
120 | 106 | # When your source code is in a subdirectory under the project root, e.g.
|
121 | 107 | # `src/`, it is necessary to specify the `package_dir` argument.
|
122 |
| - package_dir={'': 'src'}, # Optional |
123 |
| - |
| 108 | + package_dir={"": "src"}, # Optional |
124 | 109 | # You can just specify package directories manually here if your project is
|
125 | 110 | # simple. Or you can use find_packages().
|
126 | 111 | #
|
|
130 | 115 | #
|
131 | 116 | # py_modules=["my_module"],
|
132 | 117 | #
|
133 |
| - packages=find_packages(where='src'), # Required |
134 |
| - |
| 118 | + packages=find_packages(where="src"), # Required |
135 | 119 | # Specify which Python versions you support. In contrast to the
|
136 | 120 | # 'Programming Language' classifiers above, 'pip install' will check this
|
137 | 121 | # and refuse to install the project if the version does not match. See
|
138 | 122 | # https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
|
139 |
| - python_requires='>=3.6, <4', |
140 |
| - |
| 123 | + python_requires=">=3.7, <4", |
141 | 124 | # This field lists other packages that your project depends on to run.
|
142 | 125 | # Any package you put here will be installed by pip when your project is
|
143 | 126 | # installed, so they must be valid existing projects.
|
144 | 127 | #
|
145 | 128 | # For an analysis of "install_requires" vs pip's requirements files see:
|
146 | 129 | # https://packaging.python.org/discussions/install-requires-vs-requirements/
|
147 |
| - install_requires=['peppercorn'], # Optional |
148 |
| - |
| 130 | + install_requires=["peppercorn"], # Optional |
149 | 131 | # List additional groups of dependencies here (e.g. development
|
150 | 132 | # dependencies). Users will be able to install these using the "extras"
|
151 | 133 | # syntax, for example:
|
|
155 | 137 | # Similar to `install_requires` above, these must be valid existing
|
156 | 138 | # projects.
|
157 | 139 | extras_require={ # Optional
|
158 |
| - 'dev': ['check-manifest'], |
159 |
| - 'test': ['coverage'], |
| 140 | + "dev": ["check-manifest"], |
| 141 | + "test": ["coverage"], |
160 | 142 | },
|
161 |
| - |
162 | 143 | # If there are data files included in your packages that need to be
|
163 | 144 | # installed, specify them here.
|
164 | 145 | package_data={ # Optional
|
165 |
| - 'sample': ['package_data.dat'], |
| 146 | + "sample": ["package_data.dat"], |
166 | 147 | },
|
167 |
| - |
168 | 148 | # Although 'package_data' is the preferred approach, in some case you may
|
169 | 149 | # need to place data files outside of your packages. See:
|
170 | 150 | # http://docs.python.org/distutils/setupscript.html#installing-additional-files
|
171 | 151 | #
|
172 | 152 | # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
|
173 |
| - data_files=[('my_data', ['data/data_file'])], # Optional |
174 |
| - |
| 153 | + data_files=[("my_data", ["data/data_file"])], # Optional |
175 | 154 | # To provide executable scripts, use entry points in preference to the
|
176 | 155 | # "scripts" keyword. Entry points provide cross-platform support and allow
|
177 | 156 | # `pip` to create the appropriate form of executable for the target
|
|
180 | 159 | # For example, the following would provide a command called `sample` which
|
181 | 160 | # executes the function `main` from this package when invoked:
|
182 | 161 | entry_points={ # Optional
|
183 |
| - 'console_scripts': [ |
184 |
| - 'sample=sample:main', |
| 162 | + "console_scripts": [ |
| 163 | + "sample=sample:main", |
185 | 164 | ],
|
186 | 165 | },
|
187 |
| - |
188 | 166 | # List additional URLs that are relevant to your project as a dict.
|
189 | 167 | #
|
190 | 168 | # This field corresponds to the "Project-URL" metadata fields:
|
|
195 | 173 | # maintainers, and where to support the project financially. The key is
|
196 | 174 | # what's used to render the link text on PyPI.
|
197 | 175 | project_urls={ # Optional
|
198 |
| - 'Bug Reports': 'https://github.com/pypa/sampleproject/issues', |
199 |
| - 'Funding': 'https://donate.pypi.org', |
200 |
| - 'Say Thanks!': 'http://saythanks.io/to/example', |
201 |
| - 'Source': 'https://github.com/pypa/sampleproject/', |
| 176 | + "Bug Reports": "https://github.com/pypa/sampleproject/issues", |
| 177 | + "Funding": "https://donate.pypi.org", |
| 178 | + "Say Thanks!": "http://saythanks.io/to/example", |
| 179 | + "Source": "https://github.com/pypa/sampleproject/", |
202 | 180 | },
|
203 | 181 | )
|
0 commit comments