Re: info docs (was Re: Experimental Python 1.5.2c1 packages available)
On Wed, Apr 14, 1999 at 07:03:09PM -0400, Joe Block wrote:
> 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.
Hmm, in this case, I'd suggest you don't install the HTML docs as
well, since they are >5MB installed (Debian's apache doesn't yet
handle .html.gz's transparently, if I could install them gzipped, that
would be down to 1.6MB), while the info files are only 500kB.
So I think the only valid case would be installing the info files
without the html ones.
Gregor
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
Re: Experimental Python 1.5.2c1 packages available
On Wed, Apr 14, 1999 at 04:07:29PM +0200, Gregor Hoffleit wrote: > The docs are quite big (700k resp. 450k for html and info > gzipped). Is there support for splitting them in separate packages ? > Then, is there also a need for postscript resp. pdf packages ? I just grab the ps files off www.python.org whenever I want to print it. I don't use info or pdf unless it's the only choice available. I'm worried about package proliferation. It's already impossible to do "dpkg -l python\*" without getting more than a screenful. My net connection is fast enough that 700K + 450K is not a concern. However, if enough people need these formats and have slow or expensive connections, then we should provide them. But for ps, it doesn't seem necessary. Just explain in README.debian where to download them from and how to print them. Most people will delete the files after printing them anyway, and installing and uninstalling a package rather than just deleting five files is rather more work. -- -Mike Orr, [EMAIL PROTECTED]
Re: Experimental Python 1.5.2c1 packages available
On Wed, 14 Apr 1999, Gregor Hoffleit wrote:
>
> > I do. Please do include info docs.
>
> I will.
>
> The docs are quite big (700k resp. 450k for html and info
> gzipped). Is there support for splitting them in separate packages ?
> Then, is there also a need for postscript resp. pdf packages ?
>
IMHO, info and html should be regarded as being in the same footing as the
main information gathering means (but I sure understand I'm a bit biased,
since I like info much more than the mean python programmer). As for
ps/pdf, I won't tell you I feel a real need (after all, I printed my copy
of python docs this summer, at 1.5.2 alpha time, and I won't reprint them
at least until 1.6), but I think they might be useful for first time
python programmers, and I think both of us would like making their life
simpler... I stand by my earlier suggestion of a couple of
doc-pdf-{a4,letter} or doc-ps-{a4,letter}, but I'm unable to tell which
is best. Votes, please!
l.
Re: Experimental Python 1.5.2c1 packages available
On Wed, Apr 14, 1999 at 09:15:53AM +0200, 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.
I will.
Earlier python-doc packages already included info docs, but they had
been unavailable for 1.5.1, therefore they aren't included currently.
The docs are quite big (700k resp. 450k for html and info
gzipped). Is there support for splitting them in separate packages ?
Then, is there also a need for postscript resp. pdf packages ?
Gregor
Re: Experimental Python 1.5.2c1 packages available
> 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.
--
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlandshttp://www.nfg.nl
Re: Experimental Python 1.5.2c1 packages available
> "LMC" == Lorenzo M Catucci <[EMAIL PROTECTED]> writes:
LMC> I seem to remember there is now a complete info set, which I
LMC> sure would like to install for use within {x,}emacs, but I
LMC> don't know how many of debian/python users would find a need
LMC> for it.
I don't think Python is much usable without info documentation. :-)
It should be definitely included somewhere.
Milan Zamazal
--
"Having GNU Emacs is like having a dragon's cave of treasures."
Robert J. Chassell
Re: Experimental Python 1.5.2c1 packages available
On Tue, Apr 13, 1999 at 09:05:36AM -0700, Mike Orr wrote: > On Tue, Apr 13, 1999 at 01:35:02PM +0200, Gregor Hoffleit wrote: > > I have put together a set of experimental Python 1.5.2c1 packages. To use > > them with apt, try the following line: > > > > deb http://master.debian.org/~flight/python ./ > > Nope, for some reason dselect still thinks 1.5.1.999b2-1 is the current > version. My /etc/apt/sources.list looks like: Aaargh. Make that http://www.debian.org/~flight/python/ resp. (for apt access) deb http://www.debian.org/~flight/python ./ Sorry for the inconveniences! Gregor
Re: Experimental Python 1.5.2c1 packages available
On Tue, 13 Apr 1999, Gregor Hoffleit wrote:
> I have put together a set of experimental Python 1.5.2c1 packages. To use
> them with apt, try the following line:
>
[...]
>
> * Python 1.5.2 release candidate 1.
>
> * libpython1.5.so reworked. Please report any anomalities! If I don't
> get any negative feedback, the next potato packages will use a shared
> libpython for the first time in Debian history ;-)
>
Excellent!
>
> * break sketch 0.5.4. This is a problem with the new multi-threaded
> Tkinter and sketch' Pax modules. Sketch' author will try to fix this,
> in the meantime sketch will have to provide an alternative
> python-tk-nothreads package.
>
This should be thought out very well... There should be a way to tell
sketch to use a "private _tkinter", and have the standard _tkinter
available as well (IMHO)
>
> * python-doc 1.5.2. Is html enough, or should I also include
> python-doc-ps and python-doc-pdf.
>
I think that having both ps and pdf is a bit overkill; look out for
a4/letter, and maybe make two packages like python-doc-ps-a4 and
python-doc-ps-ltr instead of a single one (or pdf-a4 and pdf-letter, if
the consesus is pdf being better than ps). 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.
Have a nice forthweek.
l.
Experimental Python 1.5.2c1 packages available
I have put together a set of experimental Python 1.5.2c1 packages. To use them with apt, try the following line: deb http://master.debian.org/~flight/python ./ They are also available via plain http (this time, I included a proper index.html so that it should be possible to download them with recursive wget as well): http://master.debian.org/~flight/python/ New features: * Python 1.5.2 release candidate 1. * libpython1.5.so reworked. Please report any anomalities! If I don't get any negative feedback, the next potato packages will use a shared libpython for the first time in Debian history ;-) * break sketch 0.5.4. This is a problem with the new multi-threaded Tkinter and sketch' Pax modules. Sketch' author will try to fix this, in the meantime sketch will have to provide an alternative python-tk-nothreads package. Not yet: * The great package renaming. * jpython * python-doc 1.5.2. Is html enough, or should I also include python-doc-ps and python-doc-pdf. The next release of JPython will have a free license. Since there are some build dependencies on non-free software, JPython probably will go into contrib at first. Nevertheless, this will make it necessary to have a common python library package (python-lib ?). Again, any Gregor
