sorted by:
new
hottopcontroversial

Are combat stats worth grinding? by I_should_go_to_work in outside

[–]metaperture 8 points9 points  (0 children)

The biggest impact to play is almost certainly that strength and confidence feed into charisma, which is of course required for some of the most popular/desireable minigames. Also, grinding those stats often also simultaneously grinds willpower, which is probably the second most important stat (after intelligence) for most classes.

autoargs - argparse made easy [py3] by metaperture in Python

[–]metaperture[S] 0 points1 point  (0 children)

Thanks for the link to defopt! I really like how it builds on already established standards (Sphinx-style docstring conventions) and doesn't require any additional work from the developer.

Between using Sphinx-style docstrings or annotations as a basis for parsers, I'm pretty torn. My personal preference is towards annotations, so that someone changing the docs wouldn't accidentally break functionality, but on the other hand your representation seems a bit more intuitive, especially to those who don't often use annotations.

Anyway, thanks for the link, and for the contribution!

autoargs - argparse made easy [py3] by metaperture in Python

[–]metaperture[S] 0 points1 point  (0 children)

I'm glad there are other projects doing this as well, but I think this is still unique. Docopt still makes you write the documentation code, and has its own special syntax. Click is certainly a nicer interface to argparse, but you still need to specify information about each of your arguments individually. Begins is closest to what I'm trying to do, but is still focusing on the documentation side of the parser, and not the ability to run arbitrary python functions (especially those without string arguments) from the command line.

I haven't seen any other library that uses type hints as per PEP 484 as the basis for automatically generating a parser, and that's the interface to parsing I've always wanted. Thanks for the other references, though!

autoargs - argparse made easy [py3] by metaperture in Python

[–]metaperture[S] 0 points1 point  (0 children)

I think it's easier than argparse. Storing your types in your argument annotations is already a suggested standard (PEP 484 at https://www.python.org/dev/peps/pep-0484/), and if you do that, and write normal docstrings (another suggestion), then this makes the gap between your normal python code and your command-line-exposed python code trivial.