| commit | ac6a7d8884762d27cc2dde5a5c6e793cc18fc4d9 | |
| author | John Snow <jsnow@redhat.com> | |
| Wed, 21 Apr 2021 19:22:30 +0000 (21 15:22 -0400) | ||
| committer | Markus Armbruster <armbru@redhat.com> | |
| Fri, 30 Apr 2021 10:59:54 +0000 (30 12:59 +0200) | ||
| tree | f7f114c5aa4f3386b389f2f5651eaaa31502c8c0 | treesnapshot (tar.gz zip) |
| parent | ac89761179ed6e3165a63ad68759f77f33bace30 | commitdiff |
qapi/error.py: move QAPIParseError to parser.py
Keeping it in error.py will create some cyclic import problems when we
add types to the QAPISchemaParser. Callers don't need to know the
details of QAPIParseError unless they are parsing or dealing directly
with the parser, so this won't create any harsh new requirements for
callers in the general case.
Update error.py with a little docstring that gives a nod to where the
error may now be found.
Signed-off-by: John Snow <jsnow@redhat.com>
Message-Id: <20210421192233.3542904-6-jsnow@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Keeping it in error.py will create some cyclic import problems when we
add types to the QAPISchemaParser. Callers don't need to know the
details of QAPIParseError unless they are parsing or dealing directly
with the parser, so this won't create any harsh new requirements for
callers in the general case.
Update error.py with a little docstring that gives a nod to where the
error may now be found.
Signed-off-by: John Snow <jsnow@redhat.com>
Message-Id: <20210421192233.3542904-6-jsnow@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
| scripts/qapi/error.py | diffblobblamehistory | |
| scripts/qapi/parser.py | diffblobblamehistory |