add inline dependencies #269
@@ -1,4 +1,14 @@
|
|||||||
#!/usr/bin/env python3
|
#!/usr/bin/env python3
|
||||||
|
# /// script
|
||||||
|
# dependencies = [
|
||||||
|
# "tqdm",
|
||||||
|
# "requests",
|
||||||
|
# "dbus-python",
|
||||||
|
# "gbinder",
|
||||||
|
# "PyGObject",
|
||||||
|
# "InquirerPy"
|
||||||
|
|
|||||||
|
# ]
|
||||||
|
# ///
|
||||||
|
This introduces a second source of truth for runtime dependencies (inline here and also in This introduces a second source of truth for runtime dependencies (inline here and also in `requirements.txt`). That duplication can drift over time and cause confusing install/runtime mismatches. Consider either generating/deriving one from the other, or documenting which one is authoritative (and when each should be updated).
```suggestion
```
|
|||||||
from InquirerPy import inquirer
|
from InquirerPy import inquirer
|
||||||
from InquirerPy.base.control import Choice
|
from InquirerPy.base.control import Choice
|
||||||
from InquirerPy.separator import Separator
|
from InquirerPy.separator import Separator
|
||||||
|
|||||||
Reference in New Issue
Block a user
The inline
# /// scriptmetadata is parsed as TOML (PEP 723 style). In a TOML array, items must be comma-separated; as written, thedependencies = [block is invalid and tools likeuv run --scriptwill fail to parse it. Add commas between the dependency strings (a trailing comma is also fine).