Python作为一个函数来进行争论

问题描述

以这种方式获取命令行参数有什么内在的错误吗？我的意思是把参数解析放到它自己的函数中。它会被认为是非pythonic或更多？

Is there anything inherently wrong with getting command-line arguments in this way? I mean by putting the argument parsing into its own function. Would it be considered non-Pythonic or more so?

#!/usr/bin/python

import argparse

def getArgs(argv=None):
    parser = argparse.ArgumentParser(description="calculate X to the power of Y")
    group = parser.add_mutually_exclusive_group()
    group.add_argument("-v", "--verbose", action="store_true")
    group.add_argument("-q", "--quiet", action="store_true")
    parser.add_argument("x", type=int, help="the base")
    parser.add_argument("y", type=int, help="the exponent")
    return parser.parse_args(argv)

if __name__ == "__main__":

    argvals = None             # init argv in case not testing
    argvals = '6 2 -v'.split() # example of passing test params to parser
    args = getArgs(argvals)

    answer = args.x**args.y

    if args.quiet:
        print answer
    elif args.verbose:
        print "{} to the power {} equals {}".format(args.x, args.y, answer)
    else:
        print "{}^{} == {}".format(args.x, args.y, answer)

推荐答案

它看起来不错，感觉很好，符合 - 那么，如果你没有看到这个特定的代码，那么会出现什么问题像那样？

It looks good, feels good, conforms to Python Zen - so, what's the problem if you didn't see this particular code like that?

将一些独立的功能移入子例程是必不可少的实践 - ，确切而言。它甚至不是Python。

Moving a somewhat independent piece of functionality into a subroutine is essential good practice - a manifestation of separation of concerns, to be precise. It's not even about Python.

这篇关于Python作为一个函数来进行争论的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！