structopt VS cookiecutter

Hope you are aware that structopt is in maintenance mode and is merged into clap as of v3.

As I understood you need to implement a command line argument parser for that you can use clap https://github.com/clap-rs/clap or structopt https://github.com/TeXitoi/structopt.

I feel like discovering moves like this is a weakness in the ecosystem today. You can check out some of our discussion on raising visibility

Something I've been giving thought to is how to help structopt users discover that clap3 is their upgrade path. We've put notices in the structopt repo but cargo upgrade and docs.rs won't say anything. See https://github.com/TeXitoi/structopt/issues/525 for more ideas we're considering.

For myself, I have found serde.rs really useful for undertanding their derives while I've always been frustrated with finding anything in structopt's documentation, so I modeled it more off of serde. This ended up both being in structure and not being in docs.rs. I think it really was the structure that was the frustration point for me but there was interest elsewhere in moving stuff out of docs.rs.

I think it would be nice to have a comparison to clap-derive and/or structopt in the README, as that is what I expect most users would compare this to. The subcommand handling looks especially cumbersome compared to deriving on structs and enums.

However, the one place I'm a little curious to rewrite things is the CLI... every time we have to deal with cobra I long for Rust's structopt.

Have you tried https://github.com/TeXitoi/structopt ?

It is written in Rust using the structopt and swayipc crates. It is published on crates.io. The repository is hosted on GitLab. The repository is mirrored on GitHub.

I use structopt, which itself uses clap.

Sometimes I use this to abstract boilerplate https://github.com/cookiecutter/cookiecutter

It can use a repo as a template.

It supports some interactive questions to choose options but mostly it is jinja templates.

Having libraries would be another option.

Install the cookiecutter package using the following command:

Consider taking a look at cookiecutter to generate projects from templates. There is also cookiecutter-django. As for your environment variables you should have an example .env file containing all the environment variables required by your project (without setting them) that can be safely pushed into your repository for you and other developers to copy into the actual .env file that'll be used by your project (add this file to .gitignore)

The Python Cookiecutter library revolutionizes project development by offering streamlined approach to creating template projects and improving developer experience.

We use cookie cutter templates (the Python project, https://github.com/cookiecutter/cookiecutter ), we prompt for the module & version etc

Why not use cookiecutter or a similar tool designed for making these sorts of project templates?

Is it common? I don't know. Is it useful? Absolutely. There is a tool called cookiecutter that allows you to define your own setup. For example, my cookiecutter setup for a python library is here. You can see what it's like by first installing the cookiecutter cli and then running

Also cookiecutter.

Visual Cookiecutter enhances the functionality of cookiecutter by offering unique features such as required fields, conditional input parameters, optional descriptions, and the ability to fix mistakes easily. This package seamlessly integrates with cookiecutter so that all existing templates work out-of-the-box.