Yes, I realise my mistake... ;-)
Just out of interest, what helpful features over and above the regular
python shell does ipython/bpython provide, and how will this enhance
the Dojo..?
I don't mean to put you on the spot, but if I learned anything from
the last Dojo it was that putting people in front of unfamiliar tools
makes the Dojo more intimidating and uncomfortable (one more thing to
learn / get to grips with in addition to solving the problem at hand).
However, if it will make the Dojo easier then we must use it - I
*personally* think part of the reason for coding in public is to
discover new development tools and "wrinkles" that we can all learn
from! Perhaps we should just make it available and highlight it for
those who wish to use and demonstrate it (as Dave suggested).
Nicholas.
On 7 Oct 2009, at 09:11, Ed Singleton wrote:
On 6 Oct 2009, at 21:21, Nicholas Tollervey wrote:
As for IronPython... I suppose that'll need some thought before-
hand for the purposes of configuration. I know the Resolver guys
will be there to call on for help and I don't mind getting the
thing to run on Mono on my MacBook, but I think the whole subject
of IronPython/Jython/Pypy and cPython alternatives might be a good
subject for a show-and-tell type dojo (make your Python write once,
run everywhere).
I think he meant ipython http://ipython.scipy.org/, the interactive
python shell, not IronPython.
ipython (or bpython http://www.bpython-interpreter.org/) is a good
idea. Particularly for 'investigative' programming.
Ed
_______________________________________________
python-uk mailing list
python-uk@python.org
http://mail.python.org/mailman/listinfo/python-uk
_______________________________________________
python-uk mailing list
python-uk@python.org
http://mail.python.org/mailman/listinfo/python-uk