Save to file now outputs executable code (i.e. without the >>> and ... and with
"# OUT: " prepended to all output lines). I never used this feature much but
someone asked for this behaviour.
This had the side-effect of me discovering the showsyntaxerror method on
code.InteractiveInterpreter, which I have now overridden and passed through my
own routines, so these errors are now in the same colour as the other
exceptions. Hooray.
A bunch of people were moaning about this, I guess they couldn't handle it. It
was kind of irritating me as well, it just doesn't seem to look as nice as it
should when you've got nested calls etc., oh well.
- Use the setuptools entry_points mechanism
- Move the primary bpython script itself into the bpython module with
invocation via the setuptools entry_points mechanism.
- Fix setup.py whitespace to be consistant (4-spaces only)
- Ignore setuptools-generated build products
Oops, messed up a little. Hopefully everything's okay. I moved
internal.py to _internal.py so it isn't cluttering the namespace so
much, and also I forgot to mention that I wrote a config parser using
shlex so you can set any attribute of the OPTS object now, e.g.
auto_display_list
syntax
arg_spec
A few people pointed out that help() can cause problems, specifically
when the help string is really big, so I've internalised it and injected
my own help() function into the interpreter which pages the output, but
it's pretty ghetto so I'm open to suggestions for improvement.
That said, it's pretty obvious that scrolling up and down (like less)
would be the main requested improvement so I should get to work on that
at some point.
Pascal Bleser was kind enough to package bpython for OpenSUSE
and sent me a patch to have it working with distutils, which
is always nice, so thanks a lot for that, here's the new
dir structure.
Kenneth Reitz