Re: [Distutils] layout and setup.py for packaging documentation

2010-03-01 Thread Tarek Ziadé
On Mon, Mar 1, 2010 at 5:52 PM, Sridhar Ratnakumar wrote: > > On 2010-03-01, at 8:44 AM, Sridhar Ratnakumar wrote: > >> Is the documentation directory expected to contain files in certain format - >> for example, with a file describing the Table-of-Contents (toc.xml) that >> would then be used t

Re: [Distutils] layout and setup.py for packaging documentation

2010-03-01 Thread Sridhar Ratnakumar
On 2010-03-01, at 8:44 AM, Sridhar Ratnakumar wrote: > Is the documentation directory expected to contain files in certain format - > for example, with a file describing the Table-of-Contents (toc.xml) that > would then be used to render MSDN like doc tree? .. and/or make a single-container (e

Re: [Distutils] layout and setup.py for packaging documentation

2010-03-01 Thread Sridhar Ratnakumar
Ah, very nice! This was one of the things I wanted to discuss in the sprints. I've been mentioning this idea internally as well. Having documentation standards would ultimately benefit the user who could thus have a central place on his computer to browse documentation for installed Python pack

Re: [Distutils] layout and setup.py for packaging documentation

2010-03-01 Thread Tarek Ziadé
On Mon, Mar 1, 2010 at 1:08 PM, Jean Daniel wrote: >> As a matter of fact, we've worked on this during the sprints, and are >> preparing a proposal >> that will let people define a place for doc (and other stuff) and let >> the OS packager decide where >> it lands (with defaults per OS). > > I'll

Re: [Distutils] layout and setup.py for packaging documentation

2010-03-01 Thread Jean Daniel
> As a matter of fact, we've worked on this during the sprints, and are > preparing a proposal > that will let people define a place for doc (and other stuff) and let > the OS packager decide where > it lands (with defaults per OS). I'll read the proposal. I wonder how it is possible to layout a s

Re: [Distutils] layout and setup.py for packaging documentation

2010-03-01 Thread Marius Gedminas
On Sun, Feb 28, 2010 at 10:49:25PM -0500, P.J. Eby wrote: > In other words, Jean Daniel should retain his source layout of: > >wordish-1.0.2/ > setup.py > wordish.py > docs/ > index.html > command-ref.html > > And simply make sure that docs/ is un

Re: [Distutils] layout and setup.py for packaging documentation

2010-02-28 Thread P.J. Eby
At 10:39 PM 2/28/2010 +, Michael Foord wrote: On 28 February 2010 22:14, P.J. Eby <p...@telecommunity.com> wrote: At 10:03 PM 2/28/2010 +0100, Jean Daniel wrote: Can this be simpler? Yes. Don't install docs with your package. People who want them installed

Re: [Distutils] layout and setup.py for packaging documentation

2010-02-28 Thread Michael Foord
On 28 February 2010 23:03, Tarek Ziadé wrote: > On Sun, Feb 28, 2010 at 11:39 PM, Michael Foord > wrote: > > > > > > On 28 February 2010 22:14, P.J. Eby wrote: > >> > >> At 10:03 PM 2/28/2010 +0100, Jean Daniel wrote: > >>> > >>> Can this be simpler? > >> > >> Yes. Don't install docs with your

Re: [Distutils] layout and setup.py for packaging documentation

2010-02-28 Thread Tarek Ziadé
On Sun, Feb 28, 2010 at 11:39 PM, Michael Foord wrote: > > > On 28 February 2010 22:14, P.J. Eby wrote: >> >> At 10:03 PM 2/28/2010 +0100, Jean Daniel wrote: >>> >>> Can this be simpler? >> >> Yes.  Don't install docs with your package.  People who want them >> installed locally can just download

Re: [Distutils] layout and setup.py for packaging documentation

2010-02-28 Thread Michael Foord
On 28 February 2010 22:14, P.J. Eby wrote: > At 10:03 PM 2/28/2010 +0100, Jean Daniel wrote: > >> Can this be simpler? >> > > Yes. Don't install docs with your package. People who want them installed > locally can just download your source install or use easy_install -e. > > Also, if your modul

Re: [Distutils] layout and setup.py for packaging documentation

2010-02-28 Thread P.J. Eby
At 10:03 PM 2/28/2010 +0100, Jean Daniel wrote: Can this be simpler? Yes. Don't install docs with your package. People who want them installed locally can just download your source install or use easy_install -e. Also, if your module is popular enough that people make Linux system package