-
Notifications
You must be signed in to change notification settings - Fork 16
Python variant #42
Copy link
Copy link
Open
Labels
priority: mediumMedium priorityMedium prioritystatus: plannedPlanning to implementPlanning to implementtype: newNew feature or enhancementNew feature or enhancement
Metadata
Metadata
Assignees
Labels
priority: mediumMedium priorityMedium prioritystatus: plannedPlanning to implementPlanning to implementtype: newNew feature or enhancementNew feature or enhancement
As I'm aiming to close out #27 this week, we probably should discuss how the Python variant should be structured.
Given there are a lot of packaging tools for Python, is there a preference among the tools that should be used? e.g. Build + setuptools, Poetry, Twine, Flit, Hatch, or PDM.
If we're aiming to publish on PyPi's repository, we'll need to rename to
py-countdownascountdownis already taken by someone else. Alternatively, we could reach out and ask if they would be okay with letting us re-use the name (not sure how that would work).For the package layout, I'm thinking about something like:
. ├── LICENSE ├── pyproject.toml ├── README.md ├── src/ │ ├── countdown/ │ │ ├── __init__.py │ │ ├── countdown.py │ │ └── utils.py │ └── shiny_app/ │ ├── __init__.py │ └── app.py └── tests/