Skip to content

migrate this to a cookiecutter template? #116

Open

Description

@deven367

🚀 The feature, motivation and pitch

Instead of having a separate personalize.py, the entire personalization logic can be taken care of by cookiecutter. The size of the template will go down and it would become slightly cleaner.

Alternatives

No response

Additional context

No response

Activity

  1. epwalsh commented on Jul 28, 2023

    @epwalsh
    Contributor

    There's already tons of cookiecutter Python package templates, so I'm not sure what that would add. One thing I like about this template repo is that it's a fully functioning Python package project even before running the personalization script. So even if people don't want to use this as a template, they can browse through it on GitHub and easily pull out the pieces they like. It seems like we'd loose that if we went with cookiecutter based on the look of audreyfeldroy/cookiecutter-pypackage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions