Whilst trying to plot a scatter plot with no facecolor I was able to reliably
reproduce a segfault in mpl 0.91.2 - see below:
Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit (Intel)]
IPython 0.8.3.svn.r3001 -- An enhanced Interactive Python.
In [1]: import matplotlib
In [2]: m
at 2:45 PM, Dave Peterson wrote:
Hi John,
Sorry for sending this directly, but I'm still waiting for my matplotlib
devel mailing subscription to go through
We've just had an EPD user submit a patch for matplotlib to 'fix' a problem
they were seeing with the PSD f
TraitsBackendQt to use a BSD license because it
allows commercial (ie. non-GPL) users to use it without problems."
Darren
I think it might be worth contacting the PyQt folks (Phil Thompson)
about this. I think there might be some differences here because Phil
was the author of TraitsB
t looks like
this has never been done. Was there some other work-around that didn't
make it into the thread that obviated the need for the mentioned change?
I can confirm that the renaming of putchar to put_char does solve the
problem. I've attached a patch file, though it is against
istration
costs are for the tutorials and conference itself.
-- Dave
--
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/l
t that the new install is active.
If the setup.py uses the setup() function from distutils, then none of
that happens and Gael is right. Any previous install of matplotlib via
setuptools will go to the front of the sys.path and the new install
won't be seen.
-- Dave
-
John Hunter wrote:
> On 7/22/07, Dave Peterson <[EMAIL PROTECTED]> wrote:
>
>> Hmm, why did you choose to install enthought.debug? The current source
>> for enthought.traits requires only enthought.etsconfig (which has no
>> other dependencies) and enthoug
Dave Peterson wrote:
> It does look like one of the dependencies in enthought.traits is wrong
> then. In particular, it was thought that enthought.resource was only
> required if you actually *used* Traits UI features. I just looked at
> the code and the only import, in traits,
Replying to this, even though I replied to a later message to
enthought-dev, since this one is also cc'd to matplotlib-devel
Darren Dale wrote:
> On Sunday 22 July 2007 02:10:50 pm John Hunter wrote:
>
>> On 7/22/07, Dave Peterson <[EMAIL PROTECTED]> wrote:
>>
I did because a significant part of the overhead was in
setuptools/pkg_resources declaring namespace packages and importing from
them. In fact, in Fernando's small test script using Traits, there were
over 5,000 calls(!!!) to pkg_resources even when we'd de-eggified, but
not de-package-
I'm a bit gun-shy about doing this, I'd forecast we have Traits 3.0
officially released and on PyPI by the end of June, perhaps a week into
July.
-- Dave
-
Check out the new SourceForge.net Marketplace.
It's the
g installed with egg meta-data in
order to determine an accurate version number.
-- Dave
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Sourc
Eric Firing wrote:
> Dave Peterson wrote:
>
>> That said, given the upcoming release of Traits 3 this situation may
>> get a little crazier. T2 and T3 are not fully api compatible, though
>> they are very close. So I suspect version numbers are going to play
>&g
Darren Dale wrote:
On Monday 09 June 2008 04:04:47 pm Dave Peterson wrote:
Eric Firing wrote:
Dave Peterson wrote:
That said, given the upcoming release of Traits 3 this situation may
get a little crazier. T2 and T3 are not fully api compatible, though
they are very close
14 matches
Mail list logo
