Gael Varoquaux wrote:
> Guys, I agree with all this. It's not about the theory, but about the
> user experience. The user just types along, and doesn't read books and
> manuals. A least the average user. And we want to make it as easy as
> possible for her.
Yes, we all like that.
Which is why it
Fernando Perez wrote:
> For a while I've toyed with the idea of adding an option to ipython so
> the output prompts could use str() instead of repr(), so users who
> *deliberately* want to switch, aware of the potential conflicts, do
> so.
+1
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Michael Droettboom wrote:
> Manuel Metz wrote:
>> Hi,
>> I figured out a bug in the FancyArrow class (sorry, I didn't track it
>> down, yet). Might be related to my strange axes limits ?
>>
>> Please have a look at the attached example. As you can see, in the
>> lower panel the head is not render
Manuel Metz wrote:
> Hi,
> I figured out a bug in the FancyArrow class (sorry, I didn't track it
> down, yet). Might be related to my strange axes limits ?
>
> Please have a look at the attached example. As you can see, in the lower
> panel the head is not rendered correctly.
It appears to be s
On Thursday 13 December 2007 11:07:57 am John Hunter wrote:
> I moved the tools in mlab that did optional imports (the rec2gtk and
> rec2excel functions and their dependencies) out of mlab into
> toolkits.gtktools and toolkits.exceltools. As Michael noted, these
> imports can be expensive for user
Hi,
I figured out a bug in the FancyArrow class (sorry, I didn't track it
down, yet). Might be related to my strange axes limits ?
Please have a look at the attached example. As you can see, in the lower
panel the head is not rendered correctly.
I used the lates svn, revision 4730.
Manuel
