Skip to content

Python variant #42

@coatless

Description

@coatless

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-countdown as countdown is 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/

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions