Ok. Thanks for the information. That does do exactly what I would expect. I
would place my vote for having this be the default
behavior since this is what it means to say "go from point A to B" on a polar
plot.
--James
> -Original Message-
> From: Michael Droettboom [mailto:md...@sts
Michael Droettboom wrote:
> There seems to have been an indentation error there.
>
> Please update and try again now.
>
All seems to be fine now, thanks.
João Silva
--
This SF.net email is sponsored by:
SourcForge Com
On Mon, Feb 02, 2009 at 03:47:32PM +, Chris Walker wrote:
> One of the things I liked about Gael's article was its discussion of
> threading - separating the gui from the calculations from the data
> acquisition.
Thanks. Be aware that this is a rats nest, though, as threading is the
best way t
There seems to have been an indentation error there.
Please update and try again now.
Thanks,
Mike
João Luís Silva wrote:
> Michael Droettboom wrote:
>> Thanks for narrowing this down. I have (hopefully) fixed this in r6864.
>>
>
> It did fix my previous examples. However it broke the other for
Michael Droettboom wrote:
> Thanks for narrowing this down. I have (hopefully) fixed this in r6864.
>
It did fix my previous examples. However it broke the other form of
markevery, a 2-int tuple. From the set_markevery docs:
Set the markevery property to subsample the plot when using
You can get this behavior you are asking for by passing "resolution=1"
to polar. (This has been there for ages, but unfortunately wasn't
documented until recently). We can consider making 1 the default.
There are cases in which the automatic interpolation is useful, but in
the present impleme
Thanks for narrowing this down. I have (hopefully) fixed this in r6864.
Cheers,
Mike
João Luís Silva wrote:
> Michael Droettboom wrote:
>> Thanks for the report. I'm not actually able to reproduce this here
>> -- though I suspect this could be related to the recent path
>> simplification chan
I noticed plotfile_demo.py has recently broken. Seems to be units
related. Before I look into it further, is there an obvious fix for
anyone else?
Traceback (most recent call last):
File "plotfile_demo.py", line 18, in
plotfile(fname, (0,5,6), plotfuncs={5:'bar'})
File
"/home/mdroe/u
On Sun, Feb 01, 2009 at 11:59:06PM +0100, Sandro Tosi wrote:
> Hi Chris,
> thanks for your reply, helpful as usual :)
>
> On Fri, Jan 30, 2009 at 18:59, Chris Walker
> wrote:
> > Firstly, good luck with the book.
>
> cheers :)
>
> > The sort of book I'd buy would explain how to use the co
Michael Droettboom wrote:
> Thanks for the report. I'm not actually able to reproduce this here --
> though I suspect this could be related to the recent path simplification
> changes.
>
> Taking a stab in the dark -- have you tried removing the build directory
> and rebuilding? distutils doe
Thanks for the report. I'm not actually able to reproduce this here --
though I suspect this could be related to the recent path simplification
changes.
Taking a stab in the dark -- have you tried removing the build directory
and rebuilding? distutils doesn't do dependency-tracking, so if hea
On Mon, Feb 2, 2009 at 1:26 AM, Fernando Perez wrote:
>> I believe mpl-data/matplotlibrc is not version-controled, but created
>> when you run setup.py.
>> Maybe you're trying to build the documentation from a new svn checkout
>> but didn't build the library?
>
> Aha, that's it, thanks. I'd run
12 matches
Mail list logo
