GitHub’s Choose a License or consult a lawyer.įor an example, see the LICENSE.txt from the PyPAĪlthough it’s not required, the most common practice is to include your If you’re unsure which license to choose, you can use resources such as Not be legally used or distributed by anyone other than the copyright holder. In many jurisdictions, packages without an explicit license can LICENSE.txt ¶Įvery package should include a license file detailing the terms ofĭistribution. MANIFEST.in does not affect binary distributions such as wheels. This is not a requirement multiple variants of Markdown are supported as well (lookĪt setup()’s long_description_content_type argument).įor an example, see README.md from the PyPA The most common format is reStructuredText with an “rst” extension, although For an example, see the setup.cfg in the PyPAĪll projects should contain a readme file that covers the goal of the project. Setup.cfg is an ini file that contains option defaults for To get a listing of available commands, run It’s the command line interface for running various commands that The most relevant arguments are explained in The keyword arguments to this function are how specific details Primary feature of setup.py is that it contains a global setup()įunction. It’s the file where various aspects of your project are configured. For an example, see the setup.py in the PyPA The most important file is setup.py which exists at the root of your
Configuring your project ¶ Initial files ¶ setup.py ¶ You’ll need this to upload your project distributions to PyPI (see below). Requirements for packaging and distributing ¶įirst, make sure you have already fulfilled the requirements for Standards compliance for interoperability Requirements for packaging and distributing
0 kommentar(er)
