@steve
Thanks :)
On Mon, Feb 8, 2010 at 12:15 PM, steve wrote:
> Hi Shashwat,
>
>
> On 02/06/2010 11:20 PM, Shashwat Anand wrote:
>
>> here is the bpython screencast : http://*bpython*-
>> interpreter.org/static/*
>> bpython*-screencast01.
>> ogg
>> It's worth trying.
>>
>
> +1. (Having tried b
Hi Shashwat,
On 02/06/2010 11:20 PM, Shashwat Anand wrote:
here is the bpython screencast : http://*bpython*-interpreter.org/static/*
bpython*-screencast01.
ogg
It's worth trying.
+1. (Having tried both ipython and bpython, I prefer bpython mainly because of
the cleaner interface (ie: no unne
here is the bpython screencast : http://*bpython*-interpreter.org/static/*
bpython*-screencast01.
ogg
It's worth trying.
By the way does anyone want to share their customized Vi features with
respect to python. I am pretty much satisfied with my own but there is
always scope for improvements.
On
Hey Noufal,
I'm not sure what you mean by standard email quotations. FYI, I just went
back and checked my mail in gmail and it shows up fine, so the formatting's
not screwed up (I get a lot, when you sent it as simple text and it has a
_lot_ of *this*)
Jeff
On Sat, Feb 6, 2010 at 10:39 PM, Nouf
On Sat, Feb 6, 2010 at 7:45 PM, Jeffrey Jose wrote:
> I was under the impression that everyone here used and loved IPython. Boy,
> was I wrong.
Thanks for taking time to explain things a bit with ipython. I have
heard rave reviews about ipython, especially from the scientific
python community, wh
I'd recommend that you use standard email quotations. It makes for
better reading rather than the * notation that you've used to reply to
Senthil's mail.
On Sat, Feb 6, 2010 at 7:45 PM, Jeffrey Jose wrote:
> [ caution, huge email follows ]
>
> Hey Senthil,
> I was under the impression that everyo
Thanks. I'll give it a spin.
btw, Can you tell me why you prefer bpython over IPython and the nifty
features I should be looking for when I try bpython ?
Jeff
On Sat, Feb 6, 2010 at 7:55 PM, Shashwat Anand wrote:
> @Jeffrey,
>
> bpython is a bit unstable and crash-prone but I prefer it over Ip
@Jeffrey,
bpython is a bit unstable and crash-prone but I prefer it over Ipython.
On Sat, Feb 6, 2010 at 7:45 PM, Jeffrey Jose wrote:
> [ caution, huge email follows ]
>
> Hey Senthil,
> I was under the impression that everyone here used and loved IPython. Boy,
> was I wrong.
> I wont attempt t
Not quite long ago, I wrote,
You loose all capabilities of pdb when you're in IPython (there's a
solution, i'll get to that later)
Its called ipdb. IPythonised pdb. I havent used it to recommend it. I'm
happy with the solution that I have right now for debugging and writing
code.
Read more about
[ caution, huge email follows ]
Hey Senthil,
I was under the impression that everyone here used and loved IPython. Boy,
was I wrong.
I wont attempt to convince you folks why you should use IPython, but here a
few features that I love in IPython which are not there (or not very
obvious) in vanilla
On Thu, Feb 04, 2010 at 12:55:08PM +0530, steve wrote:
> than the standard python interface, I would recommend trying out bpython:
>
> http://bpython-interpreter.org/
This is cool. Thanks for pointing out.
--
Senthil
If you just try long enough and hard enough, you can always manage to
boot your
On 02/04/2010 05:43 AM, Senthil Kumaran wrote:
Using IPython from pdb, what use is it?
I read Jeff's excellent mail on debugging and tracing and he insisted on
using IPython from pdb. I have used pdb extensively and never used IPython,
(it never caught me, given that odd interface of number[:]) e
Using IPython from pdb, what use is it?
I read Jeff's excellent mail on debugging and tracing and he insisted on
using IPython from pdb. I have used pdb extensively and never used IPython,
(it never caught me, given that odd interface of number[:]) etc.
So, I am really not sure as how using IPytho
13 matches
Mail list logo
