Skip to content

Commit 642895f

Browse files
committed
deploy: 870f63f
1 parent 98bc76c commit 642895f

File tree

3 files changed

+2
-0
lines changed

3 files changed

+2
-0
lines changed

.doctrees/environment.pickle

0 Bytes
Binary file not shown.
Binary file not shown.

_sources/package-structure-code/pyproject-toml-python-package-metadata.md.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -183,9 +183,11 @@ what dependencies your package requires.
183183
The examples at the bottom of this page contain ...
184184

185185
- **`[project.scripts]` (Entry points):** Entry points are optional. If you have a command line tool that runs a specific script hosted in your package, you may include an entry point to call that script directly at the command line (rather than at the Python shell).
186+
186187
- Here is an example of[ a package that has entry point script](https://github.com/pyOpenSci/update-web-metadata/blob/main/pyproject.toml#L60)s. Notice that there are several core scripts defined in that package that perform sets of tasks. The pyOpenSci is using those scripts to process their metadata.
187188
- **Dynamic Fields:** if you have fields that are dynamically populated. One example of this is if you are using scm / version control based version with tools like `setuptooms_scm`, then you might use the dynamic field, such as version (using scm) **dynamic = ["version"]**
188189

190+
189191
## Add dependencies to your pyproject.toml file
190192

191193
The pyproject.toml file can also be used as a replacement for the requirements.txt file which has been traditionally used to store development dependencies such as pytest, code formatters such as Black and documentation tools such as sphinx.

0 commit comments

Comments
 (0)