info docs (was Re: Experimental Python 1.5.2c1 packages available)
Paul Stevens wrote:
>
> > I seem to remember there is now a complete info set, which I sure
> > would like to install for use within {x,}emacs, but I don't know how
> > many of debian/python users would find a need for it.
>
> I do. Please do include info docs.
How about making the info docs a seperate package? That way, if you
didn't install emacs you don't have to get the info docs - if disk is so
tight you don't want emacs you probably don't want info docs.
--
Joe Block <[EMAIL PROTECTED]>
"You're one of those condescending Unix computer users"
"Here's a nickel, kid. Get yourself a better computer" - Dilbert
task-python, proper dependencies in other python packages
David Coe wrote: > > > I do think task-python(*) makes sense. But I think a "python" package > > would just encourage people to make gratuitous overarching > > dependencies... > > Another good point. Part of the problem is that there doesn't seem to be a tool yet to automatically figure out which files your program is importing from, and what packages provide them. >task-python-bundle have the entire upstream (www.python.org) distribution > (I'm not sure I like the name '-bundle' -- if you have a better suggestion > please speak up.) task-python-standard or task-python-distribution? jpb -- Joe Block <[EMAIL PROTECTED]> CREOL System Administrator Social graces are the packet headers of everyday life.
