Hi all,
I ran into a problem where I wanted to plot a step-plot with dashed
lines instead of solid lines which can be important for print media.
This isn't possible with the current matplotlib version, so I added
support for this. The patch is attached, but I didn't commit it yet
since I wan
Manuel Metz wrote:
> Hi all,
> I ran into a problem where I wanted to plot a step-plot with dashed
> lines instead of solid lines which can be important for print media.
> This isn't possible with the current matplotlib version, so I added
> support for this. The patch is attached, but I didn'
It's funny you should mention this.
One of the things I realized after SciPy this year is that there is a
lot of interfacing of Numpy with C++ (as opposed to C) that could really
benefit from a standard C++ wrapper around Numpy. A bunch of different
projects all had home-grown, semi-complete s
Sphinx contains one way to do this in its new "pngmath" extension. It
uses the LaTeX package "preview" which does all of this magic
internally. And I believe it's a little more general. If I recall, the
approach you're taking won't work with some LaTeX constructs such as:
\begin{align}
Thanks,
I quickly went through the code of the pngmath.py, and it seems that
the depth(descent) of the dvi file is reported by "dvipng" (but the
preview package must be used in the tex file for this to work
correctly). Therefore, with this method, we need to run dvipng even if
we use ps of pdf bac
Hello Everyone
This is my first post, I really enjoy using python/numpy/scipy/matplotlib
- great replacement for matlab. I am having a problem, with plot 1 point at
a time. i am attempt to emulate an issue in the lab, where we get samples
every second and plot them. The figure becomes non-respon
On Fri, Aug 29, 2008 at 12:01 PM, Ray Salem <[EMAIL PROTECTED]> wrote:
>This is my first post, I really enjoy using python/numpy/scipy/matplotlib
> - great replacement for matlab. I am having a problem, with plot 1 point at
> a time. i am attempt to emulate an issue in the lab, where we get sa
Michael Droettboom wrote:
> It's funny you should mention this.
>
> One of the things I realized after SciPy this year is that there is a
> lot of interfacing of Numpy with C++ (as opposed to C) that could really
> benefit from a standard C++ wrapper around Numpy.
Absolutely. Though now that yo
Grégory Lielens wrote:
> Thanks a lot for reviewing my patch!
> I have corrected most of the problems (I think ;-) )
> I indeed introduced memory leak, I think it is fixed now, I have also
> reorganized the code to avoid duplication of the cleanup code. I used an
> helper function instead of the go
Christopher Barker wrote:
> Michael Droettboom wrote:
>
>> It's funny you should mention this.
>>
>> One of the things I realized after SciPy this year is that there is a
>> lot of interfacing of Numpy with C++ (as opposed to C) that could really
>> benefit from a standard C++ wrapper around N
10 matches
Mail list logo
