matplotlib-devel Mailing List for matplotlib

>
> 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 what we want.)
c is a named argument of the scatter method for the colors, but it is
modified to get the real "colors" argument.
I think that what we want may be the following:
>
> try:
> colors = colorConverter.to_rgba_list(c, alpha)
> except TypeError:
> colors = None # generate colors later by applying a colormap to c
>
> Part of what makes all this hard to understand is that in the None case,
> colors are generated from c far down in the code, out of sight of this
> initial processing. Hence the comment.
>
> OK, now I see that what I proposed won't work until I rip out the
> long-deprecated float-as-grey option. Looks like a good time for me to
> do it.
>
> Eric
If you say so :)
Matthieu

Matthieu Brucher wrote:
> Hi,
> 
> I'm trying to display a scatter plot in 3D, and it calls the 2D scatter 
> plot, in axes.py. This method tests for validity of the color argument 
> in line 3777 :
> 
> if not is_string_like(c) and iterable(c) and len(c)==len(x):
> colors = None
> else:
> colors = ( colorConverter.to_rgba(c, alpha), )
> 
> The trick is that if c is a numpy array, it passes the test, and thus no 
> color is selected. If I get rid of the test and use a Nx3 array, the 
> plot is correctly displayed.
> 
> I suppose that we could make it :
> 
> if not (is_string_like(c) or is_numlike(c)) and iterable(c) and 
> len(c)==len(x):
> colors = None
> else:
> colors = ( colorConverter.to_rgba(c, alpha), )
> 
> ?
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 what we want.)
I think that what we want may be the following:
try:
 colors = colorConverter.to_rgba_list(c, alpha)
except TypeError:
 colors = None # generate colors later by applying a colormap to c
Part of what makes all this hard to understand is that in the None case, 
colors are generated from c far down in the code, out of sight of this 
initial processing. Hence the comment.
OK, now I see that what I proposed won't work until I rip out the 
long-deprecated float-as-grey option. Looks like a good time for me to 
do it.
Eric
> 
> I found a little error in a docstring, if this proposal is OK, I'll send 
> a diff patch to the list.
> 
> Matthieu
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

John Hunter wrote:
> On 4/5/07, Robert Kern <rob...@gm...> wrote:
> 
>> The purpose of ez_setup.py was to give people a migration path such that they
>> could write project that used setuptools, but ensure that their users wouldn't
>> have to go install another package themselves.
>>
>> It's deprecated now. Don't use it.
> 
> So from this I take that our current approach advising people to use
> ez_setup.pu if setuptools are not available is also a bad idea.
> Currently we
> 
> try: import setuptools
> except ImportError:
> raise SystemExit("""\
> matplotlib requires setuptools for installation. Please download
> http://peak.telecommunity.com/dist/ez_setup.py and run it (as su if
> you are doing a system wide install) to install the proper version of
> setuptools for your system. If this is your first time upgrading
> matplotlib with the new setuptools requirement, you must delete the
> old matplotlib install directory.""")
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
-- 
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
 -- Umberto Eco

On 4/5/07, Robert Kern <rob...@gm...> wrote:
> The purpose of ez_setup.py was to give people a migration path such that they
> could write project that used setuptools, but ensure that their users wouldn't
> have to go install another package themselves.
>
> It's deprecated now. Don't use it.
So from this I take that our current approach advising people to use
ez_setup.pu if setuptools are not available is also a bad idea.
Currently we
 try: import setuptools
 except ImportError:
 raise SystemExit("""\
matplotlib requires setuptools for installation. Please download
http://peak.telecommunity.com/dist/ez_setup.py and run it (as su if
you are doing a system wide install) to install the proper version of
setuptools for your system. If this is your first time upgrading
matplotlib with the new setuptools requirement, you must delete the
old matplotlib install directory.""")

Robert Kern wrote:
> John Hunter wrote:
> 
>> On 4/5/07, Edin Salkovic <edi...@gm...> wrote:
>>
>> 
>>> This would make installing setuptools even easier, since the newest
>>> ez_setup/seuptools would be downloaded by the user/developer every
>>> time a "svn update;python setup.py install" is issued.
>>>
>>> Are the above changes OK?
>>> 
>> I'm not sure I see the benefit here -- what does it buy us to insure
>> that we always have the latest ez_setup in our tree?
>> 
>
> The purpose of ez_setup.py was to give people a migration path such that they
> could write project that used setuptools, but ensure that their users wouldn't
> have to go install another package themselves.
>
> It's deprecated now. Don't use it.
> 
Furthermore, even if it weren't deprecated, it seems to me a bad idea.
(Perhaps that's why it's deprecated.) If a user needs to install
setuptools, IMO, the user should know that. For example, on most linux
distributions, the right thing to do would be to install that
distribution's package of setuptools.

Hi,
I'm trying to display a scatter plot in 3D, and it calls the 2D scatter
plot, in axes.py. This method tests for validity of the color argument in
line 3777 :
 if not is_string_like(c) and iterable(c) and len(c)==len(x):
 colors = None
 else:
 colors = ( colorConverter.to_rgba(c, alpha), )
The trick is that if c is a numpy array, it passes the test, and thus no
color is selected. If I get rid of the test and use a Nx3 array, the plot is
correctly displayed.
I suppose that we could make it :
 if not (is_string_like(c) or is_numlike(c)) and iterable(c) and
len(c)==len(x):
 colors = None
 else:
 colors = ( colorConverter.to_rgba(c, alpha), )
?
I found a little error in a docstring, if this proposal is OK, I'll send a
diff patch to the list.
Matthieu

John Hunter wrote:
> On 4/5/07, Edin Salkovic <edi...@gm...> wrote:
> 
>> This would make installing setuptools even easier, since the newest
>> ez_setup/seuptools would be downloaded by the user/developer every
>> time a "svn update;python setup.py install" is issued.
>>
>> Are the above changes OK?
> 
> I'm not sure I see the benefit here -- what does it buy us to insure
> that we always have the latest ez_setup in our tree?
The purpose of ez_setup.py was to give people a migration path such that they
could write project that used setuptools, but ensure that their users wouldn't
have to go install another package themselves.
It's deprecated now. Don't use it.
-- 
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
 -- Umberto Eco

On 4/5/07, Edin Salkovic <edi...@gm...> wrote:
> This would make installing setuptools even easier, since the newest
> ez_setup/seuptools would be downloaded by the user/developer every
> time a "svn update;python setup.py install" is issued.
>
> Are the above changes OK?
I'm not sure I see the benefit here -- what does it buy us to insure
that we always have the latest ez_setup in our tree?
JDH

On Thursday 05 April 2007 06:44:36 am Edin Salkovic wrote:
> On 4/5/07, Darren Dale <dd...@co...> wrote:
> > I considered this when setuptools became a requirement for python-2.3
> > installs, but decided against it. My reasoning was that the unfamiliar
> > user would go to install matplotlib, and see setup.py and ez_setup and
> > get confused. Maybe it should go in a subdirectory in our tree?
>
> Just to clear things up, in case there's some misunderstanding:
> ez_setup would be a dir in both cases. You are suggesting that the
> ez_setup dir should be put somewhere other than in the current
> matplotlib toplevel dir (where 'setup.py' resides). Am I correct? 
Sorry, there is some confusion, probably on my part. I was thinking of the 
ez_setup.py file, which suggests that you can run it to install it, or drop 
it in your distribution next to setup.py, either way would be sufficient. I 
though it would be a bad idea to have a setup.py and an ez_setup.py in the 
same directory. We would get people running ez_setup.py and then writing the 
lists asking why they cant import pylab.
Darren

On 4/5/07, Darren Dale <dd...@co...> wrote:
> I considered this when setuptools became a requirement for python-2.3
> installs, but decided against it. My reasoning was that the unfamiliar user
> would go to install matplotlib, and see setup.py and ez_setup and get
> confused. Maybe it should go in a subdirectory in our tree?
Just to clear things up, in case there's some misunderstanding:
ez_setup would be a dir in both cases. You are suggesting that the
ez_setup dir should be put somewhere other than in the current
matplotlib toplevel dir (where 'setup.py' resides). Am I correct? If
so, I don't see why would anyone be confused by having an ez_setup dir
at the top level, but that's just my opinion. In fact, I think that
some of the current dirs at toplevel are more confusing ;). Anyway,
either way (toplevel or subdir) is fine for me.
ez_setup dir will be there only to aid a person that's *building from
source* (normaly a dev building from SVN), so he can allways have the
latest setuptools installed on *his* system.
A person (regular user) that doesn't have setuptools installed, and
just wants to do a "easy_install matplotlib" will still have to
download the ez_setup.py script from
http://peak.telecommunity.com/dist/ez_setup.py , and run it, before
installing matplotlib. Then, he'll soon get into the problem of not
having the appropriate backend installed, but that's another problem
:)
Cheers,
Edin

On Thursday 05 April 2007 4:29:00 am Edin Salkovic wrote:
> On 3/3/07, John Hunter <jd...@gm...> wrote:
> > On 2/23/07, Andrew Straw <str...@as...> wrote:
> > I figured I would be a good crash test dummy to see how easy
> > it was to install setuptools, so I poked around and found the ez_setup
> > and am off to the races. I added a friendly exception to setup.py to
> > make it easier for the next guy
> >
> > if major==2 and minor1<=3:
> > # setuptools monkeypatches distutils.core.Distribution to support
> > # package_data
> > try: import setuptools
> > except ImportError:
> > raise SystemExit("""\
> > matplotlib requires setuptools for installation. Please download
> > http://peak.telecommunity.com/dist/ez_setup.py and run it (as su if
> > you are doing a system wide install) to install the proper version of
> > setuptools for your system""")
>
> Apparently, there's a better solution for the above code (source
> http://peak.telecommunity.com/doc/ez_setup/index.html):
> ===
> This directory (svn://svn.eby-sarna.com/svnroot/ez_setup) exists so
> that Subversion-based projects can share a single
> copy of the ``ez_setup`` bootstrap module for ``setuptools``, and have it
> automatically updated in their projects when ``setuptools`` is updated.
>
> For your convenience, you may use the following svn:externals definition::
>
> ez_setup svn://svn.eby-sarna.com/svnroot/ez_setup
>
> You can set this by executing this command in your project directory::
>
> svn propedit svn:externals .
>
> And then adding the line shown above to the file that comes up for editing.
> Then, whenever you update your project, ``ez_setup`` will be updated as
> well. ===
>
> We should then add the following lines to our setup.py script
>
> from ez_setup import use_setuptools
> use_setuptools()
> from setuptools import setup, find_packages
>
> This would make installing setuptools even easier, since the newest
> ez_setup/seuptools would be downloaded by the user/developer every
> time a "svn update;python setup.py install" is issued.
>
> Are the above changes OK?
I considered this when setuptools became a requirement for python-2.3 
installs, but decided against it. My reasoning was that the unfamiliar user 
would go to install matplotlib, and see setup.py and ez_setup and get 
confused. Maybe it should go in a subdirectory in our tree?

On 4/5/07, Bill Baxter <wb...@gm...> wrote:
> So I suggest instead 'npy'. It is already used extensively in the C
> API of Numpy so it has strong precedent as an abbreviation. It also
> *looks* to me like an abbreviation for 'numpy' as opposed to "number
> of points (np)" or something else. Having 3 letters also makes it
> slightly less likely to clash with typical short user variable names.
+1 for npy.

On 3/3/07, John Hunter <jd...@gm...> wrote:
> On 2/23/07, Andrew Straw <str...@as...> wrote:
> I figured I would be a good crash test dummy to see how easy
> it was to install setuptools, so I poked around and found the ez_setup
> and am off to the races. I added a friendly exception to setup.py to
> make it easier for the next guy
>
> if major==2 and minor1<=3:
> # setuptools monkeypatches distutils.core.Distribution to support
> # package_data
> try: import setuptools
> except ImportError:
> raise SystemExit("""\
> matplotlib requires setuptools for installation. Please download
> http://peak.telecommunity.com/dist/ez_setup.py and run it (as su if
> you are doing a system wide install) to install the proper version of
> setuptools for your system""")
Apparently, there's a better solution for the above code (source
http://peak.telecommunity.com/doc/ez_setup/index.html):
===
This directory (svn://svn.eby-sarna.com/svnroot/ez_setup) exists so
that Subversion-based projects can share a single
copy of the ``ez_setup`` bootstrap module for ``setuptools``, and have it
automatically updated in their projects when ``setuptools`` is updated.
For your convenience, you may use the following svn:externals definition::
 ez_setup svn://svn.eby-sarna.com/svnroot/ez_setup
You can set this by executing this command in your project directory::
 svn propedit svn:externals .
And then adding the line shown above to the file that comes up for editing.
Then, whenever you update your project, ``ez_setup`` will be updated as well.
===
We should then add the following lines to our setup.py script
from ez_setup import use_setuptools
use_setuptools()
from setuptools import setup, find_packages
This would make installing setuptools even easier, since the newest
ez_setup/seuptools would be downloaded by the user/developer every
time a "svn update;python setup.py install" is issued.
Are the above changes OK?

On 4/4/07, Eric Firing <ef...@ha...> wrote:
> If you want to make one more release, I would like to have a few days
> notice to see if I can clear up at least one thing, and maybe a couple more.
OK, let's shoot for a release next week or the week after, however
long it takes for people to get their current work into svn, tested
and stable, and (optionally) include a deprecation warning for Numeric
and numarray users. The we can get started with the numpy migration
in svn, with the view that we can take our time with it, and try and
get something out in six weeks or so. By that time, Perry and crew
will be almost ready to push out their numpy based release and their
users will be minimally inconvenienced, if at all.
JDH