Hi,
I've made some progress on an MPL canvas infrastructure built on top of the
contains() methods patch I submitted earlier (and now in svn).
I would like to post it to svn so that interested parties can play with it
and contribute to the development, but it is not yet ready to be put in the
On Sun, Jul 15, 2007 at 10:49:13PM -0400, Paul Kienzle wrote:
I don't see an obvious way to remove a line from an axes object.
Shall I add remove_child(h) which searches through all the lists
of containers and removes the one that I don't want?
I think that would be very useful. TVTK has
This morning I am having trouble installing from the svn repository. My home
machine does not have setuptools installed, and the standard python setup.py
install fails because it wants to import setuptools.
If I install setuptools, I am able to install, but not run pylab:
In [1]: from pylab
On 7/15/07, Paul Kienzle [EMAIL PROTECTED] wrote:
Hi,
I don't see an obvious way to remove a line from an axes object.
Shall I add remove_child(h) which searches through all the lists
of containers and removes the one that I don't want?
That's one way to do it, but you might consider
I am cleaning up some of the code in ticker.ScalarFormatter, specifically some
of the text formatting for dealing with scientific notation.
We provide an option to format labels in sci. notation without using mathtext
or usetex, in which case I would like to use the unicode multiplication
Darren Dale wrote:
If not, should we use
u'\xd7' or '×' in the actual sources (the latter requiring the file's
encoding to be declared at the beginning of the file, like: # -*- coding:
utf-8 -*-)?
In an ideal world, I would prefer the latter, but we would want to
verify that all the
On 7/16/07, Eric Firing [EMAIL PROTECTED] wrote:
I use a good old-fashioned editor called zed, written by an Italian
named Sandro Serrafini who seems to have left no trace for several
years. I have modified it slightly, and I do minimal maintenance to
keep it compiling with new OS releases.
John Hunter wrote:
On 7/16/07, Eric Firing [EMAIL PROTECTED] wrote:
I use a good old-fashioned editor called zed, written by an Italian
named Sandro Serrafini who seems to have left no trace for several
years. I have modified it slightly, and I do minimal maintenance to
keep it compiling
Darren Dale wrote:
[...]
What about rendering unicode, but keeping the mpl sources ascii only?
This sounds like the thing to do for now.
While you are at it, perhaps you can figure out how to stop unicode_demo
from generating an error:
driving unicode_demo.py
File
It looks like Edin made setuptools required in svn, which I just
reverted. Edin -- why? I'm a fan of setuptools, but I don't think we
should require a prerequisite that isn't necessary. Of course, if the
developers decide we want to require setuptools, I'm happy to support
the change, but it
I'm working on some improvements to the mathtext engine on a branch.
Feel free to join in if curious, but I expect to break lots of things as
I go.
https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/branches/mathtext_mgd/
I've collected a bunch of math expressions from the source tree
Eric Firing wrote:
While you are at it, perhaps you can figure out how to stop
unicode_demo from generating an error:
driving unicode_demo.py
File _tmp_unicode_demo.py, line 10
SyntaxError: Non-ASCII character '\xe9' in file _tmp_unicode_demo.py
on line 10, but no encoding
On 7/16/07, Michael Droettboom [EMAIL PROTECTED] wrote:
As for Unicode literals in Python source, there is a third option, other
than u'\xd7' or '×'. Python will let you do u\N{MULTIPLICATION SIGN},
which means you don't have to remember what \xd7 is. For single
characters like this, I don't
On Monday 16 July 2007 02:32:30 pm John Hunter wrote:
On 7/16/07, Michael Droettboom [EMAIL PROTECTED] wrote:
I'm working on some improvements to the mathtext engine on a branch.
Feel free to join in if curious, but I expect to break lots of things as
I go.
I've been thinking a bit about rcParams and validation. It looks like values
are currently only validated when matplolibrc is read, during the call to
rc_params. What if we define a new class (RcParams), derived from dict, which
has as an attribute, a dict, called validate. We could override
Darren Dale wrote:
I've been thinking a bit about rcParams and validation. It looks like values
are currently only validated when matplolibrc is read, during the call to
rc_params. What if we define a new class (RcParams), derived from dict, which
has as an attribute, a dict, called
On Monday 16 July 2007 7:22:37 pm you wrote:
Darren Dale wrote:
I've been thinking a bit about rcParams and validation. It looks like
values are currently only validated when matplolibrc is read, during the
call to rc_params. What if we define a new class (RcParams), derived from
dict,
On 7/16/07, Darren Dale [EMAIL PROTECTED] wrote:
John wrote rc_traits.py, before numpy was around, by the looks of it. Traits
seem more appealing to me than properties, but I was looking for something
that could be done outside of a chainsaw branch. If we decided on traits, we
should also try
On 7/16/07, Darren Dale [EMAIL PROTECTED] wrote:
John wrote rc_traits.py, before numpy was around, by the looks of it. Traits
seem more appealing to me than properties, but I was looking for something
that could be done outside of a chainsaw branch. If we decided on traits, we
should also try
John Hunter wrote:
[...]
Isn't there a potential problem here? The original validate funcs
support conversion from a string to a value, but you are proposing
using them here in a context where users will generally be supplying a
(possibly bogus) value, but in general not a string. So the
John Hunter wrote:
On 7/16/07, Eric Firing [EMAIL PROTECTED] wrote:
Are any real, live projects outside of enthought making major use of
traits? Or would we be the first?
Yes. Most are in the somewhat formative stages, so you may not think they count
(which is fine).
I am happy to be the
21 matches
Mail list logo
