Hello all,
I managed to merge my docfix/improve_description branch over to v1.0.x, but
I am having trouble merging correctly over to master. It appears that the
README.osx and make.osx files were changed in v1.0.x, but not in master. So
my merge wants me to resolve these differences -- which I a
Yes. IPython certainly has what looks like a reasonable "recipe" to
support PySide and PyQt4. I would much prefer this approach. Anything
to keep the number of code paths down in the different backends is well
worth the effort.
Mike
From: Peter Butter
There's also this git command I just discovered. It seems to solve all of
these issues, and the documentation is written in the same crystal-clear style
of the other git manpages:
http://wingolog.org/archives/2011/03/28/git-brunch1
Mike
From: Paul Ivano
Blast from the past!
I just ran into this and it comes from the fact that
'matplotlib.tests.test_text' is not in the default_test_modules
variable inside matplotlib's __init__.py
Here's the necessary diff:
index 82633a5..649e4d8 100644
--- a/lib/matplotlib/__init__.py
+++ b/lib/matplotlib/__init
Georges Arsouze, on 2011-03-16 09:48, wrote:
> Hello
> I'am working with Python3.1 under Mac Os Snow Leopard
> I download matplotlib with
> http://www.cgl.ucsf.edu/Outreach/pc204/matplotlib.html
>
> It doesn't work
> Can you help me ?
Hi Georges,
What version of matplotlib are you trying to run
I found that
def set_sort_zpos(self,val):
'''Set the position to use for z-sorting.'''
self._sort_zpos = val
was missing from
class Line3DCollection(LineCollection) (in matplotlib 1.0.1):
Now, with the above method added, add_collection3d works as it should with
line
segments, an
Yo,
On Mon, Mar 28, 2011 at 8:17 AM, Michael Droettboom wrote:
> There's also this git command I just discovered. It seems to solve all of
> these issues, and the documentation is written in the same crystal-clear
> style of the other git manpages:
>
> http://wingolog.org/archives/2011/03/28/g
Hello all,
I just noticed a small change in behavior with 3d plots. If one creates the
plot in the old way (i.e., "ax = Axes3D(fig)"), the plot will start out
using the entire figure region as it should. However, once you start to
manipulate it (rotate or whatever), the plot loses its horizontal
I don't know if a cherry-pick is required -- just someone who understands the
changes and knows how the merge should be performed. Back in the SVN days, we
encouraged the authors making changes on the maintenance branch to merge into
trunk (master), since they were best equipped to make judgmen
Benjamin Root writes:
> I managed to merge my docfix/improve_description branch over to v1.0.x, but
> I am having trouble merging correctly over to master. It appears that the
> README.osx and make.osx files were changed in v1.0.x, but not in
> master.
That was me: those changes don't apply c
Jouni K. Seppänen writes:
> I tried to merge my changes into master with the no-op "ours" strategy
> to prevent exactly this kind of problems while waiting for the other
> request to move forward, but apparently I didn't do it right. I'll take
> a look tonight (but right now I must attend to othe
On Mon, Mar 28, 2011 at 2:02 PM, Jouni K. Seppänen wrote:
> Jouni K. Seppänen writes:
>
> > I tried to merge my changes into master with the no-op "ours" strategy
> > to prevent exactly this kind of problems while waiting for the other
> > request to move forward, but apparently I didn't do it r
Looking forward, supporting the Python 3 compatible PyQt API is likely the
way to go.
Le , Gerald Storer a écrit :
On 28/03/2011 1:10 AM, Peter Butterworth wrote:
Wouldn't it be possible to use a single backend compatible with both
PyQt and Pyside ?
The current Qt mpl backend uses t
13 matches
Mail list logo
