matplotlib-devel Mailing List for matplotlib

>>>>> "Varun" == Varun Hiremath <var...@ii...> writes:
 Varun> Hello all, Is there any way to set numpoints for each line
 Varun> in a plot. I wanted to plot 6 curves in a single plot some
 Varun> plots with continuous lines using marker='-' and some using
 Varun> symbols and line combination like using marker ='-^'. Now
 Varun> if I use legend(numpoints=1) I see one symbol for the plots
 Varun> with '-^' in the legend but I don't see anything for the
 Varun> plots with marker='-'. I want to set numpoints=4 for
 Varun> continuous lines and numpoints=1 for the one with symbols.
There isn't any support for this, and there is no obvious way to me to
add it, sorry to say.
JDH

Hello all,
 Is there any way to set numpoints for each line in a plot. I wanted to
plot 6 curves in a single plot
some plots with continuous lines using marker='-' and some using symbols and
line combination like
using marker ='-^'. Now if I use legend(numpoints=1) I see one symbol for
the plots with '-^' in the legend
but I don't see anything for the plots with marker='-'.
 I want to set numpoints=4 for continuous lines and numpoints=1 for the one
with symbols.
Regards
Varun
-- 
Varun Hiremath
Undergraduate Student,
Aerospace Engg. Department,
Indian Institute of Technology Madras,
Chennai, India
--------------------------------------------------------------------
web page : http://varun.travisbsd.org

On Mon, Oct 30, 2006 at 12:37:42PM -0700, Fernando Perez wrote:
> Jut to clarify, Gael: in ipython (with -pylab or -{g,w,q}thread), what
> happens is that IPython lets the GUI toolkit run in the main thread,
> and then attaches its own routines for user code execution as the
> toolkit's idle timer callback and runs in a secondary thread (each
> toolkit has its own way of doing this, but the basic idea is the
> same).
OK, similar to launching a wx application and starting a thread in it
with ipython attached to this thread ? Is there a "hook" to the main
eventloop that would be accessible to the code running in ipython. Thus
a wx.CallAfter or alike in different toolkits, and other eventloop and
multi-threaded programming tricks might be useful here. Maybe this
solution would even provide the solution for blocking calls with MPL
with most multi-threaded cases.
The problem I hit in my first attempt was that the "connect" call
executed in my function did not seem to be executed until the function
returned. If I can connect a callback to the figure in the beginning of
the function, then loop waiting and checking a parameter the will be set
be the callback, then process the parameter when available.
I do not see why this could not work, but then my understanding of
multithreaded programming is quite poor.
> This two-thread arrangement has a big drawback: the inability to
> interrupt long-running calculations (even non-blocking ones) with
> Ctrl-C, because it is simply impossible in Python to toss asynchronous
> signals accross threads.=20
Yes :-<. Have you tried getting some help from a guru, it seems to be
worth the while.
Cheers,
Ga=C3l

On 10/30/06, Gael Varoquaux <gae...@no...> wrote:
> On Mon, Oct 30, 2006 at 10:36:09AM -0800, Christopher Barker wrote:
> > However, perhaps you can take advantage of a similar feature (at least
> > in wx) -- can you make the Frame Modal temporarily? My understanding of
> > how model dialogs work is that they stop the main event loop, and then
> > have their own event loop, for just that frame -- then you could catch
> > the mouse event you want, and make it non-modal again.
>
> I far as I have seen in ipython the execution of a script blocks the
> eventloop. Now in another shell if the shell is not aware of the event
> loop, calling show() will block until the windows is closed (that might be
> a good blocking call for my purpose). This leaves us with the case where
> the shell is a wx shell and lives in the eventloop. A wx guru would
> probably give us the solution here.
Jut to clarify, Gael: in ipython (with -pylab or -{g,w,q}thread), what
happens is that IPython lets the GUI toolkit run in the main thread,
and then attaches its own routines for user code execution as the
toolkit's idle timer callback and runs in a secondary thread (each
toolkit has its own way of doing this, but the basic idea is the
same).
The only blocking that you see comes from blocking code which your
scripts may call (typically extension code, C, Fortran, etc), since at
that point the Python interpreter can't switch out of this secondary
thread. But as long as your scripts do NOT call any extension
blocking code, the Python interpreter will switch out every 100
bytecodes between your user code and the main thread.
This two-thread arrangement has a big drawback: the inability to
interrupt long-running calculations (even non-blocking ones) with
Ctrl-C, because it is simply impossible in Python to toss asynchronous
signals accross threads. And yes, I've tried even using the
undocumented Python C-API for cross-thread asynchronous signals via
this recipe:
http://sebulba.wikispaces.com/recipe+thread2
I spent some time on this, unsuccessfully. I still don't understand
why it doesn't work, since what I'm trying to do seems to be exactly
what that recipe is for. If anyone ever gets this to work, *please*
send it to me. It would be a major usability improvement to get
interruptibility of long computations in the threaded Pylab
environments (GTK, QT and Wx). In fact, this is part of the reason
why I'm resisting a switch to Wx: I really hate not being able to
cleanly stop a computation that is taking longer than I meant, or
which I accidentally started.
Cheers,
f

On Mon, Oct 30, 2006 at 10:36:09AM -0800, Christopher Barker wrote:
> However, perhaps you can take advantage of a similar feature (at least=20
> in wx) -- can you make the Frame Modal temporarily? My understanding of=
=20
> how model dialogs work is that they stop the main event loop, and then=20
> have their own event loop, for just that frame -- then you could catch=20
> the mouse event you want, and make it non-modal again.
I far as I have seen in ipython the execution of a script blocks the
eventloop. Now in another shell if the shell is not aware of the event
loop, calling show() will block until the windows is closed (that might b=
e
a good blocking call for my purpose). This leaves us with the case where
the shell is a wx shell and lives in the eventloop. A wx guru would
probably give us the solution here.
Now I am probably talking nonsense, as I don't know much about gui and
event loop, but it does look like there might be a solution (and the
chances that I actually implement this are close to zero, given my
knowledge of these things).
 Ga=C3l

Gael Varoquaux wrote:
> I think that for such a blocking call to work, all we would need is a
> way to start and stop the eventloop (I am talking in wx terms, the only
> GUI toolkit I know).
That's a trick, because if you stop the event loop, then you don't get 
the mouse clicks...
However, perhaps you can take advantage of a similar feature (at least 
in wx) -- can you make the Frame Modal temporarily? My understanding of 
how model dialogs work is that they stop the main event loop, and then 
have their own event loop, for just that frame -- then you could catch 
the mouse event you want, and make it non-modal again.
What I don't know is if you can make a Frame model/non-model without 
hiding and showing it in the process...
I also don't know if other toolkits work similarly.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

I've posted this patch to SF.net. It's a small change to
Axes3DI.autoscale_view brings its interface into conformity with its
parent class. More details on the SF patch.
-Andrew

>>>>> "Gael" == Gael Varoquaux <gae...@no...> writes:
 Gael> On Mon, Oct 30, 2006 at 08:21:20AM -0600, John Hunter wrote:
 >> blocking calls in pylab with gtk threading may be possible but
 >> it is beyond my powers. I would write this with a callback, eg
 >> create a class that takes a callback in the constructor and
 >> calls the callback after n clicks with a list of n coords.
 Gael> Yes this is the right way of doing this (I have been
 Gael> experimenting a bit yesterday). However have a blocking call
 Gael> would be really nice for casual programmers, like so many
 Gael> physicists, who have no idea what eventloops and threads
 Gael> are.
 Gael> I think that for such a blocking call to work, all we would
 Gael> need is a way to start and stop the eventloop (I am talking
 Gael> in wx terms, the only GUI toolkit I know). That way when a
 Gael> script call ginput the ginput call adds a few callbacks to
 Gael> the canvas (that's the easy part) and starts the
 Gael> eventloop. The callbacks stop the eventloop when the right
 Gael> number of points as been acquired.
 Gael> Now I have no clue if this is possible, but that would
 Gael> certainly make writing small interactive scripts much
 Gael> easier.
Nadia pursued blocking calls for a while and I think she made some
progress. You are right about this model fitting the brain of
physicists better than a callback approach. Maybe Nadia can bring us
up to speed on where she left off.
JDH

On Mon, Oct 30, 2006 at 08:21:20AM -0600, John Hunter wrote:
> blocking calls in pylab with gtk threading may be possible but it is
> beyond my powers. I would write this with a callback, eg create a
> class that takes a callback in the constructor and calls the callback
> after n clicks with a list of n coords.
Yes this is the right way of doing this (I have been experimenting a bit
yesterday). However have a blocking call would be really nice for casual
programmers, like so many physicists, who have no idea what eventloops
and threads are.
I think that for such a blocking call to work, all we would need is a
way to start and stop the eventloop (I am talking in wx terms, the only
GUI toolkit I know). That way when a script call ginput the ginput call
adds a few callbacks to the canvas (that's the easy part) and starts the
eventloop. The callbacks stop the eventloop when the right number of
points as been acquired.
Now I have no clue if this is possible, but that would certainly make
writing small interactive scripts much easier.
Cheers,
Ga=EBl

>>>>> "Andrew" == Andrew Colombi <co...@ui...> writes:
 Andrew> My real question is, how do I go about incorporating my
 Andrew> change to matplotlib's source repository. I've already
 Andrew> checked out the latest matplotlib/trunk/matplotlib, and
 Andrew> created a SourceForge account. When I do an svn commit it
 Andrew> doesn't give me permission. How do I get permission? If
 Andrew> someone on this list is responsible for granting write
 Andrew> access then my SF account name is andrewcc and my password
 Andrew> is... just kidding ;-) I'm not that much of a newbie, but
 Andrew> I've never submitted code to an open source project before
 Andrew> (unless you could Wikipedia).
The best way os to post a svn diff to this list and to the sourceforge
site. When you post to this list, post a link to the sf patch so we
can easily close it after we apply it.
JDH

>>>>> "Gael" == Gael Varoquaux <gae...@no...> writes:
 Gael> For those who have never used matlab, ginput is a blocking
 Gael> call that takes one optional argument n, waits for n click
 Gael> on the current figure, and returns the coordinates of those
 Gael> n clicks. I have been trying to write such a function in
 Gael> pylab and I can't find a solution.
blocking calls in pylab with gtk threading may be possible but it is
beyond my powers. I would write this with a callback, eg create a
class that takes a callback in the constructor and calls the callback
after n clicks with a list of n coords. blocking input calls may be
easier in tkagg. If there is a gtk/threading guru on hand, I'd be
interested if anyone has ideas on how to do this.
JDH

For those who have never used matlab, ginput is a blocking call that
takes one optional argument n, waits for n click on the current figure,
and returns the coordinates of those n clicks. I have been trying to
write such a function in pylab and I can't find a solution.
Here is a first attempt:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
from pylab import *
from time import sleep
class gInput(object):
 """ Class that create a callable object to retrieve mouse click in a
 blocking way, =E0 la MatLab.
 """
 def on_click(self, event):
 """ Event handler that will be passed to the current figure to
 retrive clicks.
 """
 print "called"
 if event.inaxes:
 self.clicks.append((event.x, event.y))
 print self.clicks
 def __call__(self, n):
 """ Blocking call to retrieve n coordinate pairs through mouse
 clicks.
 """
 assert isinstance(n, int), "Requires an integer argument"
 connect('button_press_event', self.on_click)
 self.clicks =3D []
 tmp =3D 0
 while len(self.clicks)<n :
 sleep(0.1)
 tmp +=3D 1
 if tmp =3D=3D 100:
 break
 return self.clicks
ginput =3D gInput()
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++=
++
I run this in ipython -pylab.
This fails. I am not to sure why. It seems the "connect" does not happen
until the __call__ function returns. This is probably due to
eventloop/thread problems that I don't master terribly well. Is there a
solution for this problem (ie a blocking call to retrieve coordinates).
If so it would be great to have such a function in pylab.
Cheers,
Ga=EBl

Hi, I found a bug in Axes3DI.autoscale_view. It does not have formal
parameters named and scalex, scaley that Axes.plot assumes (line
2115). I've added these parameters (and a scalez for completeness)
and everything works fine.
My real question is, how do I go about incorporating my change to
matplotlib's source repository. I've already checked out the latest
matplotlib/trunk/matplotlib, and created a SourceForge account. When
I do an svn commit it doesn't give me permission. How do I get
permission? If someone on this list is responsible for granting write
access then my SF account name is andrewcc and my password is... just
kidding ;-) I'm not that much of a newbie, but I've never submitted
code to an open source project before (unless you could Wikipedia).
Thanks,
-Andrew

I wrote a matplotlib Boa constructor plug-in. It is very easy to add it into
a wxframe, sizers etc in Boa constructor. 
If you are interested in the plugin, pls. send e-mail to kh...@in.... 
Igor Khromushin
-- 
View this message in context: http://www.nabble.com/Boa-Constructor-Plug-in-for-Matplotlib-tf2519521.html#a7027240
Sent from the matplotlib - devel mailing list archive at Nabble.com.

This release is compiled against numpy-1.0 final. The binaries are
fresh on sourceforge, so they may take some time to propagate to the
mirrors.
http://cheeseshop.python.org/pypi/matplotlib/
http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474
Note: There is a compile error on python2.3 that will probably require
a slight modification to the released source. Please allow some time
for us to fix this and post the binaries.
===============================================================
2006年10月26日 Released 0.87.7 at revision 2835
2006年10月25日 Made "tiny" kwarg in Locator.nonsingular much smaller - EF
2006年10月17日 Closed sf bug 1562496 update line props dash/solid/cap/join
 styles - JDH
2006年10月17日 Complete overhaul of the annotations API and example code -
 See matplotlib.text.Annotation and
 examples/annotation_demo.py JDH
2006年10月12日 Committed Manuel Metz's StarPolygon code and
 examples/scatter_star_poly.py - JDH
2006年10月11日 commented out all default values in matplotlibrc.template
 Default values should generally be taken from defaultParam in
 __init__.py - the file matplotlib should only contain those values
 that the user wants to explicitly change from the default.
 (see thread "marker color handling" on matplotlib-devel)
2006年10月10日 Changed default comment character for load to '#' - JDH
2006年10月10日 deactivated rcfile-configurability of markerfacecolor
 and markeredgecolor. Both are now hardcoded to the special value
	 'auto' to follow the line color. Configurability at run-time
	 (using function arguments) remains functional. - NN
2006年10月07日 introduced dummy argument magnification=1.0 to
 FigImage.make_image to satisfy unit test figimage_demo.py
 The argument is not yet handled correctly, which should only
	 show up when using non-standard DPI settings in PS backend,
	 introduced by patch #1562394. - NN
2006年10月06日 add backend-agnostic example: simple3d.py - NN
2006年09月29日 fix line-breaking for SVG-inline images (purely cosmetic) - NN
2006年09月29日 reworked set_linestyle and set_marker
	 markeredgecolor and markerfacecolor now default to
	 a special value "auto" that keeps the color in sync with
	 the line color
	 further, the intelligence of axes.plot is cleaned up,
	 improved and simplified. Complete compatibility cannot be
	 guaranteed, but the new behavior should be much more predictable
	 (see patch #1104615 for details) - NN
2006年09月29日 changed implementation of clip-path in SVG to work around a
 limitation in inkscape - NN
2006年09月29日 added two options to matplotlibrc:
	 svg.image_inline
	 svg.image_noscale
	 see patch #1533010 for details - NN
2006年09月29日 axes.py: cleaned up kwargs checking - NN
2006年09月29日 setup.py: cleaned up setup logic - NN
2006年09月29日 setup.py: check for required pygtk versions, fixes bug #1460783 - SC

Hey all. I am building the windows binaries of mpl-0.87.7 and I am
running into a problem with python2.3 that I have never ran into
before. I don't have too much time debug it, so I was wondering if
anyone made changes to _isnan? There is a linking error for it, and
it appears a python2.4+ dependency was added.
Thanks,
 Charlie
gcc -mno-cygwin -O2 -Wall -Wstrict-prototypes -Iwin32_static\include -I. -Ic:\Py
thon23\include -Ic:\Python23\PC -c src/_isnan.c -o build\temp.win32-2.3\Release\
src\_isnan.o
g++ -mno-cygwin -shared build\temp.win32-2.3\Release\src\_isnan.o -Lwin32_static
\lib -Lc:\Python23\libs -Lc:\Python23\PCBuild -lpython23 -o build\lib.win32-2.3\
matplotlib\_isnan.pyd
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x20):_isnan.c: undefined refere
nce to `_imp__PyArg_ParseTuple'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x55):_isnan.c: undefined refere
nce to `_imp___Py_TrueStruct'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x5d):_isnan.c: undefined refere
nce to `_imp___Py_TrueStruct'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x71):_isnan.c: undefined refere
nce to `_imp___Py_ZeroStruct'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x79):_isnan.c: undefined refere
nce to `_imp___Py_ZeroStruct'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0xbd):_isnan.c: undefined refere
nce to `_imp__Py_InitModule4'
collect2: ld returned 1 exit status
error: Command "g++ -mno-cygwin -shared build\temp.win32-2.3\Release\src\_isnan.
o -Lwin32_static\lib -Lc:\Python23\libs -Lc:\Python23\PCBuild -lpython23 -o buil
d\lib.win32-2.3\matplotlib\_isnan.pyd" failed with exit status 1

We are very pleased to announce the release of NumPy 1.0 available for 
download at http://www.numpy.org
This release is the culmination of over 18 months of effort to allow 
unification of the Numeric and Numarray communities. NumPy provides the 
features of both packages as well as comparable speeds in the domains 
where both were considered fast --- often beating both packages on 
certain problems. If there is an area where we can speed up NumPy then 
we are interested in hearing about the solution.
NumPy is essentially a re-write of Numeric to include the features of 
Numarray plus more. NumPy is a C-based extension module to Python that 
provides an N-dimensional array object (ndarray), a collection of fast 
math functions, basic linear algebra, array-producing random number 
generators, and basic Fourier transform capabilities.
Also included with NumPy are:
1) A data-type object. The data-type of all NumPy arrays are defined by 
a data-type object that describes how the block of memory that makes up 
an element of the array is to be interpreted. Supported are all basic 
C-types, structures containing C-types, arrays of C-types, and 
structures containing structures of C-types. Data-types can also be in 
big or little-endian order. NumPy arrays can therefore be constructed 
from any regularly-sized chunk of data. A chunk of data can also be a 
pointer to a Python object and therefore Object arrays can be 
constructed (including record arrays with object members).
2) Array scalars: there is a Python scalar object (inheriting from the 
standard object where possible) defined for every basic data-type that 
an array can have.
2) A matrix object so that '*' is re-defined as matrix-multiplication 
and '**' as matrix-power.
3) A character array object that can replace Numarray's similarly-named 
object. It is basically an array of strings (or unicode) with methods 
matching the string and unicode methods.
4) A record array that builds on the advanced data-type support of the 
basic array object to allow field access using attribute look-up as well 
as to provide more ways to build-up a record-array.
5) A memory-map object that makes it easier to use memory-mapped areas 
as the memory for an array object.
6) A basic container class that uses the ndarray as a member. This 
often facilitates multiple-inheritance.
7) A large collection of basic functions on the array.
8) Compatibility layer for Numeric including code to help in the 
conversion to NumPy and full C-API support.
9) Compatibility layer for NumPy including code to help in the 
conversion to NumPy and full C-API support.
NumPy can work with Numeric and Numarray installed and while the three 
array objects are different to Python, they can all share each other's 
data through the use of the array interface.
As the developers for Numeric we can definitively say development of 
Numeric has ceased as has effective support. You may still find an 
answer to a question or two and Numeric will be available for download 
as long as Sourceforge is around so and code written to Numeric will 
still work, but there will not be "official" releases of Numeric for 
future versions of Python (including Python2.5).
The development of NumPy has been supported by the people at STScI who 
created Numarray and support it. They have started to port their 
applications to NumPy and have indicated that support for Numarray will 
be phased out over the next year.
You are strongly encouraged to move to NumPy. The whole point of NumPy 
is to unite the Numeric/Numarray development and user communities. We 
have done our part in releasing NumPy 1.0 and doing our best to make the 
transistion as easy as possible. Please support us by adopting NumPy. 
If you have trouble with that, please let us know why so that we can 
address the problems you identify. Even better, help us in fixing the 
problems.
New users should download NumPy first unless they need an older package 
to work with third party code. Third-party package writers should 
migrate to use NumPy. Though it is not difficult, there are some things 
that have to be altered. Several people are available to help with that 
process, just ask (we will do it free for open source code and as 
work-for-hire for commercial code).
This release would not have been possible without the work of many 
people. Thanks go to (if we have missed your contribution please let 
us know):
 * Travis Oliphant for the majority of the code adaptation (blame him 
for code problems :-) )
 * Jim Hugunin, Paul Dubois, Konrad Hinsen, David Ascher, Jim Fulton 
and many others for Numeric on which the code is based.
 * Perry Greenfield, J Todd Miller, Rick White, Paul Barrett for 
Numarray which gave much inspiration and showed the way forward.
 * Paul Dubois for Masked Arrays
 * Pearu Peterson for f2py and numpy.distutils and help with code 
organization
 * Robert Kern for mtrand, bug fixes, help with distutils, code 
organization, and much more.
 * David Cooke for many code improvements including the auto-generated 
C-API and optimizations.
 * Alexander Belopolsky (Sasha) for Masked array bug-fixes and tests, 
rank-0 array improvements, scalar math help and other code additions
 * Francesc Altet for unicode and nested record tests and much help 
with rooting out nested record array bugs.
 * Tim Hochberg for getting the build working on MSVC, optimization 
improvements, and code review
 * Charles Harris for the sorting code originally written for Numarray 
and for improvements to polyfit, many bug fixes, and documentation strings.
 * Robert Cimrman for numpy.distutils help and the set-operations for 
arrays
 * David Huard for histogram code improvements including 2-d and d-d code
 * Eric Jones for sundry subroutines borrowed from scipy_base
 * Fernando Perez for code snippets, ideas, bugfixes, and testing.
 * Ed Schofield for matrix.py patches, bugfixes, testing, and docstrings.
 * John Hunter for code snippets (from matplotlib)
 * Chris Hanley for help with records.py, testing, and bug fixes.
 * Travis Vaught, Joe Cooper, Jeff Strunk for administration of 
numpy.org web site and SVN
 * Andrew Straw for bug-reports and help with www.scipy.org
 * Albert Strasheim for bug-reports, unit-testing and Valgrind runs
 * Stefan van der Walt for bug-reports, regression-testing, and 
bug-fixes.
 * Eric Firing for bugfixes.
 * Arnd Baecker for 64-bit testing
 * A.M. Archibald for code that decreases the number of times reshape 
makes a copy.
More information is available at http://numpy.scipy.org and 
http://www.scipy.org. Bug-reports and feature requests should be 
submitted as tickets to the Trac pages at 
http://projects.scipy.org/scipy/numpy/
As an anti-SPAM measure, you must create an account in order to post 
tickets.
Enjoy the new release,
Sincerely,
The NumPy Developers
*Disclaimer*: The main author, Travis Oliphant, has written a 350+ page 
book entitled "Guide to NumPy" that documents the new system fairly 
thoroughly. The first two chapters of this book are available on-line 
for free, but the remainder must be purchased (until 2010 or a certain 
number of total sales has been reached). See http://www.trelgol.com for 
more details. There is plenty of free documentation available now for 
NumPy, however. Go to http://www.scipy.org for more details.

Hello,
I have the following script and in matplotlib 0.87.5 (debian sid) and text is not
correctly displayed, whereas in matplotlib 0.82-1 it was ok. See attached
pictures.
#!/usr/bin/python
# -*- coding: iso-8859-2 -*-
from pylab import *
ab = unicode('żłóńę','iso-8859-2')
plot([1, 3, 4],[1, 4, 2])
xlabel(ab)
show()
I found that the problem occurs when I have GTKAgg, WXAgg or PS backends set in
matplotlibrc file and matplotlib displays fonts properly when using
GTK, WX as backend. So I guess that it must be something wrong with recent
antigrain or preparing text for agg rendering.

The latest word on the numpy list is that numpy-1.0 is coming out on
Wednesday. I suggest waiting until the final 1.0 release is out
before we do a new matplotlib build. I will try to push a build asap
after that. Are there any show stoppers lingering that would delay a
release? I would also suggest we refrain from any major commits.
Charlie

Unfortunately, I forgot to do it :(
Then, just after sending the message to the list, it sprang to my
mind. To make it worse, I then mistakenly entered:
rm -Rf /path/to/site-packages
no matplotlib at the end, and hit enter.
There goes my beautiful Python install. :'(
Is there some switch to setup.py to make it remove the mpl dir or does
one allways have to do it by hand?
Cheers,
Edin
On 10/22/06, Darren Dale <dd...@co...> wrote:
> Did you try deleting your old mpl directory from site-packages, remove the
> build directory from you mpl sources, and rebuild from scratch?
>
>
>
> On Sunday 22 October 2006 6:59 am, Edin Salkovic wrote:
> > Hi,
> >
> > I built and installed the latest matplotlib from SVN.
> >
> > When I type:
> > >>> from pylab import *
> > >>> plot([1,2,3])
> >
> > I get:
> >
> > Traceback (most recent call last):
> > File "<stdin>", line 1, in ?
> > File "/usr/lib/python2.4/site-packages/matplotlib/pylab.py", line
> > 2027, in plot
> > ret = gca().plot(*args, **kwargs)
> > File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
> > 2131, in plot self.autoscale_view(scalex=scalex, scaley=scaley)
> > File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
> > 985, in autoscale_view
> > self.set_xlim(XL)
> > File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
> > 1227, in set_xlim
> > self.viewLim.intervalx().set_bounds(xmin, xmax)
> > TypeError: only length-1 arrays can be converted to Python scalars.
> >
> > I'm using Numeric as numerix. I'm on a Ubuntu box with python 2.4.
> >
> > -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, security?
> > Get stuff done quickly with pre-integrated technology to make your job
> > easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
> > Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
> --
> Darren S. Dale, Ph.D.
> dd...@co...
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Did you try deleting your old mpl directory from site-packages, remove the 
build directory from you mpl sources, and rebuild from scratch?
On Sunday 22 October 2006 6:59 am, Edin Salkovic wrote:
> Hi,
>
> I built and installed the latest matplotlib from SVN.
>
> When I type:
> >>> from pylab import *
> >>> plot([1,2,3])
>
> I get:
>
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "/usr/lib/python2.4/site-packages/matplotlib/pylab.py", line
> 2027, in plot
> ret = gca().plot(*args, **kwargs)
> File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
> 2131, in plot self.autoscale_view(scalex=scalex, scaley=scaley)
> File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
> 985, in autoscale_view
> self.set_xlim(XL)
> File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
> 1227, in set_xlim
> self.viewLim.intervalx().set_bounds(xmin, xmax)
> TypeError: only length-1 arrays can be converted to Python scalars.
>
> I'm using Numeric as numerix. I'm on a Ubuntu box with python 2.4.
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Darren S. Dale, Ph.D.
dd...@co...

Hi,
I built and installed the latest matplotlib from SVN.
When I type:
>>> from pylab import *
>>> plot([1,2,3])
I get:
Traceback (most recent call last):
 File "<stdin>", line 1, in ?
 File "/usr/lib/python2.4/site-packages/matplotlib/pylab.py", line
2027, in plot
 ret = gca().plot(*args, **kwargs)
 File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
2131, in plot self.autoscale_view(scalex=scalex, scaley=scaley)
 File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
985, in autoscale_view
 self.set_xlim(XL)
 File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line
1227, in set_xlim
 self.viewLim.intervalx().set_bounds(xmin, xmax)
TypeError: only length-1 arrays can be converted to Python scalars.
I'm using Numeric as numerix. I'm on a Ubuntu box with python 2.4.

Just a heads up, numpy-1.0rc3 breaks compatibility. :(
- Charlie

I've created a further patch concerning custom symbols. The patch is
attached, as well as an example and the script producing it.
First what it does:
- you can now create custom line-symbols, which is useful to create e.g.
S-shaped symbols, see example:
 pylab.scatter(x,y,s=120,marker=(verts,2))
- you can now create asterisk-like symbols
 pylab.scatter(x,y,s=80,marker=(5,2))
Additionally I've corrected the scaling of custom verts.
However, there is problem with the asterisk symbols I'm not sure how to
solve, and I ask for your advice!!! As you can see in the attached
example output, custom_symbol2a.png, the length of the arms of the
asterisk-symbol appear different even so have numerically all the same
length. An asterisk-symbol is drawn by connecting the origin (0,0) with
one end of an arm, e.g. (1,0) and again back to the origin (0,0), then
to the next end of an arm and so on.
- Is there a better way to do this?
- And is there a way to avoid output artefacts like those in the example
attached ?
The artefact seems to be present for a pixel-devices only (like .png)
but not for a vector-drawing-device like eps :-( So it seems that it is
an issue of rounding to int ???
Manuel

Hi,
I'm not quite sure, but I think there is a bug in backend_agg.py in the
function draw_point(). I got an error when trying to use this function,
and the attached patch fixed the problem. As you can see, it seems that
there is just a parameter (rotation) missing.
Manuel