It appears Circle has lost it's verts attribute, but not all of the
references.
-r
PyMate r6190 running Python 2.5 (/usr/bin/env python)
>>> picker_demo.py
Exception in Tkinter callback
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
pytho
On 4/5/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Oh, you're requiring setuptools now? I didn't notice that. Cool.
>
> I'd point them here for up-to-date instructions and downloads:
>
> http://cheeseshop.python.org/pypi/setuptools
Thanks Robert for the insight! I updated the installation
inst
Robert Hetland <[EMAIL PROTECTED]> writes:
> It appears Circle has lost it's verts attribute, but not all of the
> references.
Fixed in svn revision 3162 by replacing .verts with .get_verts().
However get_verts() indicates that it is "[n]ot actually used for
rendering", so perhaps this is not
I just noticed there was a bug report about the pdf backend in the
tracker, but that was just by accident, since the reported had not
sent email to either of the mailing lists. Is there any way of getting
email about new bugs from Sourceforge, or maybe an RSS feed or
something?
--
Jouni K. Seppän
Hi all,
I'm getting:
planck[examples]> python pylab_segfault.py
Numpy version: 1.0.3.dev3651
Segmentation fault (core dumped)
with this trivial code
planck[examples]> cat pylab_segfault.py
import sys
import numpy as N
import pylab as P
print "Numpy version:",N.__version__
sys.stdout.flush()
On 4/6/07, Fernando Perez <[EMAIL PROTECTED]> wrote:
> planck[examples]> python pylab_segfault.py
> Numpy version: 1.0.3.dev3651
> Segmentation fault (core dumped)
> sudo rm -rf build
> sudo python setup.py install
let us know
On Friday 06 April 2007 04:37:46 pm Fernando Perez wrote:
> import sys
> import numpy as N
> import pylab as P
>
> print "Numpy version:",N.__version__
> sys.stdout.flush()
>
> P.imshow(N.ones((4,4),dtype=N.uint8))
> P.show()
Yep, I also see it, with svn 3163. It looks like the problem is only wit
On 4/6/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> On Friday 06 April 2007 04:37:46 pm Fernando Perez wrote:
> > import sys
> > import numpy as N
> > import pylab as P
> >
> > print "Numpy version:",N.__version__
> > sys.stdout.flush()
> >
> > P.imshow(N.ones((4,4),dtype=N.uint8))
> > P.show()
>
>
Matthieu Brucher wrote:
> I don't quite understand: what kind of "c" are you passing in, what is
> the original code doing with it, and what should it do with it? (I find
> both the original and the suggested code hard to understand, which makes
> me think that neither is actually
Fernando Perez wrote:
> On 4/6/07, Darren Dale <[EMAIL PROTECTED]> wrote:
>> On Friday 06 April 2007 04:37:46 pm Fernando Perez wrote:
>>> import sys
>>> import numpy as N
>>> import pylab as P
>>>
>>> print "Numpy version:",N.__version__
>>> sys.stdout.flush()
>>>
>>> P.imshow(N.ones((4,4),dtype=N
Fernando Perez wrote:
> On 4/6/07, Darren Dale <[EMAIL PROTECTED]> wrote:
>> On Friday 06 April 2007 04:37:46 pm Fernando Perez wrote:
>>> import sys
>>> import numpy as N
>>> import pylab as P
>>>
>>> print "Numpy version:",N.__version__
>>> sys.stdout.flush()
>>>
>>> P.imshow(N.ones((4,4),dtype=N
Hi Eric,
> Unless I hear shortly that someone else is already fixing this, or that
> I am misdiagnosing the problem, I will proceed. It may be that checking
> for 3-D needs to be done earlier in the mpl python code as well, but it
> certainly seems like it should be done here.
I was just on the
Fernando Perez wrote:
> Hi Eric,
>
>> Unless I hear shortly that someone else is already fixing this, or that
>> I am misdiagnosing the problem, I will proceed. It may be that checking
>> for 3-D needs to be done earlier in the mpl python code as well, but it
>> certainly seems like it should be
On 4/6/07, Eric Firing <[EMAIL PROTECTED]> wrote:
> OK, but I don't have any record of Nick Young's email address--if
> someone knows it, please send it to me.
I found this in my gmail archive:
Nicholas Young <[EMAIL PROTECTED]>
Cheers,
f
--
This is done (with corresponding simplification of the code and improved
error checking and reporting), and I have made slight changes to
scatter, but there is still an ambiguity in scatter's argument handling.
It was and is resolved in favor of treating the c argument as an array
rather than a
Fernando Perez wrote:
> Hi all,
>
>
> I'm getting:
>
> planck[examples]> python pylab_segfault.py
> Numpy version: 1.0.3.dev3651
> Segmentation fault (core dumped)
>
>
> with this trivial code
>
> planck[examples]> cat pylab_segfault.py
> import sys
> import numpy as N
> import pylab as P
>
On 4/6/07, Eric Firing <[EMAIL PROTECTED]> wrote:
> I have fixed this in two ways: by raising an exception in _image.cpp if
> the input to frombyte lacks 3 dimensions--this prevents the
> segfault--and by checking uint8 arrays for 3 dimensions in image.py
> before sending them to frombyte in the f
Matthieu Brucher wrote:
> This is done (with corresponding simplification of the code and improved
> error checking and reporting), and I have made slight changes to
> scatter, but there is still an ambiguity in scatter's argument handling.
> It was and is resolved in favor of tre
18 matches
Mail list logo
