I currently use ArgSpec to munge both definitions and calls to a common type of format. In a lot of cases,
def bob(kw=1, *args):
pass
and
bob(kw=1, *args)
Are useful to be parsed into a common format so I can quickly get the defined keywords plus any special args.
With 3.5, the difference between definitions and calling are much different due to various unpacking shortcuts. So it would make sense to kind of create an abstraction here that accomodates those difference but still allows me to use a common interface while dealing with the args.
Plus, with the differences between 3.4 and 3.5, I'd need something to buffer me from the underlying implementation. This goes a long with the creating my own ast issue. #2
Right now, I pretty much only support 3.5, after having only support 3.4. Personally IDC, but at some point I'd like to clean this up.
I currently use ArgSpec to munge both definitions and calls to a common type of format. In a lot of cases,
and
Are useful to be parsed into a common format so I can quickly get the defined keywords plus any special args.
With 3.5, the difference between definitions and calling are much different due to various unpacking shortcuts. So it would make sense to kind of create an abstraction here that accomodates those difference but still allows me to use a common interface while dealing with the args.
Plus, with the differences between 3.4 and 3.5, I'd need something to buffer me from the underlying implementation. This goes a long with the creating my own ast issue. #2
Right now, I pretty much only support 3.5, after having only support 3.4. Personally IDC, but at some point I'd like to clean this up.