Hi Alexander, Thanks for sharing your thoughts. As I'm sure you understand, free software being what it is, it's quite rare to get something that feels like a finished, polished product if you're not paying for it. I'm the original author of bpython and I haven't touched the code in several years. The remaining development is slow, driven by a handful of people who like the project enough to contribute their time to it. There's no real incentive to make it suit anyone other the people who work on it.
I don't really use Python much any more (I only code at work, and work has moved away from Python) so I have very little incentive to improve the project. I think it's easy to mistake a handful of people who like a project and don't mind adding a few tweaks to it now and then for a professional team of developers working under a project leader. Sending us an email telling us why you don't use it is unlikely to make us do anything to improve it (more accurately: make it suit you) because whether you use it or not frankly makes no real difference to us. I only say that because it's true; it's not supposed to sound snarky ! :) So, in one sentence, I'm afraid it comes down to the all-too-familiar response you've probably seen dozens of times: if you don't like it, fork it and fix it yourself. We'll gladly accept pull requests. :) Hope your holiday season is treating you well; all the best ! P.S. if you wanted to donate something in the region of $3000 I would probably be interested in picking up the issues you mentioned. I hope that puts it in perspective for you. ;) On 27 December 2014 at 19:52, <alexander.maz...@gmail.com> wrote: > I usually avoid tool upgrades - because nothing ever works like you want > it to, and the upgrade to tool X save 10seconds per task A, ends up costing > an entire day of configuration. But it finally seemed time to switch from > the default python interactive shell to something else. The two > alternatives are IPython and Bpython. Both of which support a bunch of > rather advanced features - and neither of which support some very obvious > things. > a) Lack of CodeBlock history recall > One of these very obvious things (and among the more pressing reasons to > switch from the default Pyton Interactive Shell) is code block rather than > line wise recall - Javascript consoles do this, the default Julia > interactive console does this, It's a very obvious and needed feature and > one that's very noticeably lacking (and I'm sure I'm not the only one). > b) Autocomplete has very unusable completion options > For one, I don't think most people need to see the command arguments and > __doc__ for the *print* it or *abs* functions while they are typing them > - but setting 'auto_display_list': False, will still do single tab > completion - which more properly should only display the list on tab and > complete on double-tab if there is more than one possible option (i.e. the > way fish shell tab-completion works). FUZZY, SUBSTRING, completion produce > completely unusable results, there is no frequency based history > completion. > c) various minor complaints > -The key-combo to exit b-python doesn't work if the line is not empty - > (in regular python interactive shell, the first keyboard interrupt will > wipe the current line, the second one will exit) - and there doesn't seem > to be a regular interrupt (wiping the line is not the same, if you want to > cancel a whole block of input). > -Ctrl arrows no longer move one word left or right. > -History is shared - this might be nice, maybe 20% of the time, but if you > are working on two completely different things in different sessions it's > very awkward to have one session's history show up in another. > -Sparse documentation > > I don't mean this to sound like a rant or anything of the sort, I really > want to like BPython, I like it's simplicity better than IPython, and > over-time if I keep using Bpython I would probably work on some of these > things. At any-rate I didn't want to start a bunch of separate threads for > what might be very possibly my own subjective criticisms. > > -- > You received this message because you are subscribed to the Google Groups > "bpython" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to bpython+unsubscr...@googlegroups.com. > To post to this group, send email to bpython@googlegroups.com. > Visit this group at http://groups.google.com/group/bpython. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "bpython" group. To unsubscribe from this group and stop receiving emails from it, send an email to bpython+unsubscr...@googlegroups.com. To post to this group, send email to bpython@googlegroups.com. Visit this group at http://groups.google.com/group/bpython. For more options, visit https://groups.google.com/d/optout.
