Doesn't work well though.

in IMPORT_FROM; move/convert slice statement tests.

for 3.6 and 3.7

when needed.

pyvm2 isn't Python2-ish and there is no pyvm3.

* Added YIELD event type in vmtrace
* "return" returns returned value to trace program
* *except" returns execption to trace program.
* Have to back off later Python 3.x-isms like FileNotFoundError and
  anotation signatures.

* Exception names have changed
* Catch uncaught execptions at the end when no tracing
* Lint-like fixes

R# with '#' will be ignored, and an empty message aborts the commit.

Implement provisional CALL_METHOD and LOOKUP_METHOD
Makefile now removes test/.python-version
fix a VMTrace bug in resuming a frame.

README.rst: update with new output
byteop25.py: lint

To make the interface compatible with run_python_file

to take account into additional arguments needed by instruction_info().

FIXME: something is weird with byteop33.py RAISE_VARARGS.py -
it shouldn't need a subtract one.

vm.py: was erroneously setting frame.fallthrough unconditionally after carefully
considering what value it should be - oops.

For now don't use docstring in Module since that is getting picked up in
Python's stdlib unit tests

Go over 3.3 excludes

* It was introduced in 2.7 (not 2.5).
* Add opcode docstring
* Convert native __enter__/__exit__ in context manager to Function

TODO: Add unit tests for pyobj things

Set __qualname__ where appropriate
Only set annotations and kwdefaults if >= 3.0

This is a major milestone in cross Pythonversion interpreting working.

Correct access in throwing PyVMError in opcodes.
add an async test for later.

and fix bug in instructions tracing.

so we can replace it with something that colorizes.

One callback signature mismatched was fixed too.

linestarts is a frame-oriented thing, not a vm thing.
Store callback in f_trace.

TODO: use that instead of the vm's callback more pervasively.

Todo: need to see if we can convert code objects between versions

The main goal is to improve MAKE_FUNCTION so that it make our VM
functions more often. That's not achieved totally yet. But in the
interim.

split out test_callback() into its own test
Makefile; fix bug in cleaning pyc's
byteop34.py: set dot_zero (.0) in comprehensions

blacken some buffers

Otherwise when the frame is modified in exception handling, e.g. frame.f_lastI we modify the traceback information which is wrong.

We understand how to do properly.

byterun uses six.raise which requires a real traceback and
LOAD_NAME raises NameError which makes six.raise work.

However down the line we really want to separate interpreter exceptions
from interpreted exceptions.

Right now, we can't do that - sigh.

Move do_raise() from out ouf byteop32.py and into byteop.py

Also started a cross-version inspect library.

using modified stdlib inspect.py routines.

We still have some work to get 3.7 to understand 2.7 functions,
but we're probably close.

and reinstate test_suppressed_raise_in_context_manager.py for 3.5+

These now work in 3.6 & 3.7

We can now pull off values from the frame eval stack when formatting an
instruction.

byteop.py: Move UNARY_OPERATORS, BINARY_OPERATORS, and INPLACE_OPERATORS into
byteops.

There are still the SLICE operators still in vm.py though

README.rst: update RsT formatting

in SETUP_WITH

and go over README.rst since log infomation has been improved.

the formatting changes to test_closures.py should help track down a
cross-version interpreting bug.