text: Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
  You can subscribe to this list here.
  Showing
  5
  results of 5
  John Hunter wrote:
  >>>>>>!
  Minor fix needed to avoid unpleasant surprises for users who have the old
  scipy on their import path:
  try:
  import scipy
  if hasattr(scipy,'__core_version__'):
  NUMERIX.append('scipy')
  except ImportError:
  pass
  You want to make sure that you only do this for users of the _new_ scipy, not
  the old one.
  Cheers,
  f
  >>>>> ! In the near term, this means that mpl would compile three
  shared object files for each of the three array objects for each
  extension module, which of course will increase compile times and
  binary distribution sizes. Travis, Perry, Todd and I have been
  discussing the benefits of changing matplotlib to work *only* with the
  new scipy, which include faster build times, smaller binaries, less
  complexity and pushing the community to a single array object. Since
  the new array interface works with Numeric 24, recent numarray or the
  new scipy, *any* of these array packages would work with a matplotlib
  compiled just for scipy. We decided to hold off on doing this until
  scipy installations issues were sorted out even on semi-obscure
  platforms -- Travis, what's your sense of this?
  So my inclination is to include your patch now, during a transition
  period, and then move over to a new scipy only build, retaining the
  numerix layer so Numeric, numarray and (new) scipy users can continue
  to use mpl transparently. In particular we need to make sure that
  basemap which uses numarray.ndimage continues to work.
  Does this sound like the right approach?
  JDH
  >>>>> "Charlie" == Charlie Moad <cwmoad@...> writes:
  Charlie> Awesome, thanks! Out of curiousity... did you figure
  Charlie> this out visually or by comparing with something?
  Let's just say I've encountered the flipy bug before :-)
  JDH
  Awesome, thanks! Out of curiousity... did you figure this out
  visually or by comparing with something?
  - Charlie
  On 11/18/05, John Hunter <jdhunter@...> wrote:
  > >>>>> "Charlie" =3D=3D =3D (int)aggRenderer->get_height();
  > //...
  > desty =3.
  There are some issues with parallel installation.
  I have only tested this with a python installation that
  has only the new scipy. In principle, this should be
  compatible with a parallel installation of scipy and
  numarray, but scipy and Numeric will not work, because
  I select to build extensions only for one or the other.
  d