matplotlib-devel Mailing List for matplotlib

On Saturday 03 March 2007 12:43:53 pm you wrote:
> On 2/23/07, Andrew Straw <str...@as...> wrote:
> > 2) make our own distutils monkeypatch a la setuptools. Looking at
> > setuptools/dist.py, this doesn't look trivial -- certainly beyond my
> > free bandwidth capacity.
>
> This is fine by me -- I actually was forced to think about this this
> morning as I tried to upgrade my powerbook to the latest svn. =A0I'm
> still on python2.3, and when I tried to install I hit the setuptools
> import. =A0I 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. =A0I added a friendly exception to setup.py to
> make it easier for the next guy
>
> if major=3D=3D2 and minor1<=3D3:
> =A0 =A0 # setuptools monkeypatches distutils.core.Distribution to support
> =A0 =A0 # package_data
> =A0 =A0 try: import setuptools
> =A0 =A0 except ImportError:
> =A0 =A0 =A0 =A0 raise SystemExit("""\
> matplotlib requires setuptools for installation. =A0Please 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""")

Excellent, I was going to add a warning like this myself if the setuptools=
=20
approach was accepted.

> Darren, do you still have the html docs building on your system? =A0If
> so, perhaps you could update the installing page to mention the
> requirement (an perhaps the user's guide). =A0I updated the README in
> the src distro. =A0I still haven't got my build pipeline for the htdocs
> and user's guide going on my laptop after my old build computer died,
> a good indication that both are too complicated....

Yes, I am set up to build the html docs (in fact, I have been working a bit=
 on=20
the users guide this morning.) I'll update the webpage this afternoon.

Darren

On 2/23/07, Andrew Straw <str...@as...> wrote:

> 2) make our own distutils monkeypatch a la setuptools. Looking at
> setuptools/dist.py, this doesn't look trivial -- certainly beyond my
> free bandwidth capacity.

This is fine by me -- I actually was forced to think about this this
morning as I tried to upgrade my powerbook to the latest svn.  I'm
still on python2.3, and when I tried to install I hit the setuptools
import.  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""")

Darren, do you still have the html docs building on your system?  If
so, perhaps you could update the installing page to mention the
requirement (an perhaps the user's guide).  I updated the README in
the src distro.  I still haven't got my build pipeline for the htdocs
and user's guide going on my laptop after my old build computer died,
a good indication that both are too complicated....

JDH

On 3/3/07, Jouni K. Sepp=E4nen <jk...@ik...> wrote:

> Done. Should the function signature in the docstring of barh be
> changed as well? I think listing the possible keyword arguments and
> their defaults is valuable in the help text, but the signature could
> make people think they can use positional arguments.

The call signature in the docstring should certainly be changed to
match the new signature.  Also, take a look at the kwdocd stuff we
have to see if you can make that work for the keyword args.  See
Axes.plot for an example, where we interpolate the Line2D keyword arg
docstring into the __doc__ attribute.

Thanks,
JDH

"John Hunter" <jd...@gm...> writes:

>> I replaced most of the kwargs by a **kwargs dict in svn revision 3037.
>
> Since this changes the API, albeit minimally, make sure these changes
> are documented in the API_CHANGES file.  Thanks for working on this.

Done. Should the function signature in the docstring of barh be
changed as well? I think listing the possible keyword arguments and
their defaults is valuable in the help text, but the signature could
make people think they can use positional arguments.

-- 
Jouni K. Seppänen
http://www.iki.fi/jks

On 3/3/07, Jouni K. Sepp=E4nen <jk...@ik...> wrote:

> I replaced most of the kwargs by a **kwargs dict in svn revision 3037.
> This does change the behavior for people who were giving positional
> arguments to barh, but they do get an error message.

Since this changes the API, albeit minimally, make sure these changes
are documented in the API_CHANGES file.  Thanks for working on this.

JDH

Eric Firing <ef...@ha...> writes:

> Looks like barh just needs to take a **kwargs (which could replace most 
> of the present listed kwargs; or add a log kwarg to the list) and pass 
> it along to bar.  You are taking care of this?

I replaced most of the kwargs by a **kwargs dict in svn revision 3037.
This does change the behavior for people who were giving positional
arguments to barh, but they do get an error message.

-- 
Jouni K. Seppänen
http://www.iki.fi/jks