Message413139
> In my idea it would not be a list of things that you have to pass
> piecemeal to request specific behaviour, but another function or a new
> param (like `parse(string, universal=True)`) that implements universal
> parsing.
If I'm correct in my understanding of a universal parse function (a
function with all the SchemeClasses enabled unilaterally), some
parse_universal function would be a pretty trivial thing to add with the
API I've already got here (though it wouldn't address 22852 without some
extra work afaict). I do think keeping the 'piecemeal' options exposed
has some utility, though, especially since the uses_* lists already
treat them on such a granular level.
Do we think a parse_universal function would be helpful to add on top of
this, or just repetitive? |
|
Date |
User |
Action |
Args |
2022-02-12 18:11:25 | lincolnauster | set | recipients:
+ lincolnauster, brett.cannon, orsenthil, eric.araujo, lukasz.langa |
2022-02-12 18:11:25 | lincolnauster | link | issue46337 messages |
2022-02-12 18:11:25 | lincolnauster | create | |
|