escapyde VS blackjack

Personally I split this up even further nowadays into a separate group for tests (such as here).

It's a bit too late for me to give a proper explanation right now, but if an example repository is enough: https://github.com/Diapolo10/escapyde

The established convention is to have metadata files in the repository root, and the project source code nested a level deeper. escapyde would be a fairly simple example of that.

Well, my GitHub profile is part of my flair in this subreddit, feel free to dig around. My latest project was an attempt to port the ms JavaScript library to Python, and I think I did alright. Other things I can highlight would be my iplib3 package, a server implementation for the EguiValet messaging service, and finally I've got a fairly unfinished text colouring utility called escapyde.

I wrote something similar for escapyde, which could be repurposed to do exactly that. See the escape_format function.

I don't have any Twine examples of my own, but here's one using GitHub Actions to upload files to PyPI: https://github.com/Diapolo10/escapyde

Take my escapyde-project as a small example. The README is at least somewhat helpful, the code files are in a dedicated folder while the root just contains metadata, the dependencies are properly listed in pyproject.toml (could be just requirements.txt in your case, if you want to keep things simple), and the code itself is split across multiple files to make it easier to find what you're looking for. Though admittedly I haven't had time to write proper documentation for it.

Here's one of my own that's pretty small but decently designed: https://github.com/Diapolo10/escapyde

While not quite an executable, you can take a look at my escapyde library as an example. In every release I've bundled in a pre-compiled wheel (analogous to your executable), and a source distribution. Anyone can freely download any of these.

If we take a closer look at your code, such as Blackjack (why's it called "asda" btw?), the game state is global and it would be tricky to verify everything works with unit tests. There are some... interesting design decisions like how all loop flags use one-character variable names, and you use the oldest kind of string formatting Python has ever had (tip: look into f-strings).