CPAN functionality for python - requirements

[Sean Reifschneider]

On Tue, Feb 27, 2001 at 02:49:40AM -0700, Bruce Sass wrote:
>Even if the RPM was made by someone who didn't have a clue?

Yes, because it's easier to remove an RPM from somone who doesn't have a
clue than a .tar file from somone who doesn't have a clue.

>Wouldn't it be better to have a standard way to convert a Python
>package into an RPM, that way any packaging problems will be seen by
>everyone and the fix will be fast.

The thing about automated systems is that they often fail in particularly
spetacular ways.  If that happens an human intervention is required, then
the archive network should be able to handle it, without requiring that
distutils be fixed, then handed off to the author of the package to make
a new release from.

>Huh, there are tools and standards.
>Isn't /usr/shar/doc/package the FHS place for general package specific

Where are the tools for turning doc-strings into HTML, and how are the
links between doc packages handled?  What is the markup format for the
doc strings?

We spent quite a while discussing the sad state of the documentation at our
last pythoneers meeting.  Mark Lutz was shocked that people would actually
use javadoc, but they do seem to simply becuase it was available and was
"good enough".

We are missing similar functionality.

Sean
-- 
 Give me immortality or give me death!
Sean Reifschneider, Inimitably Superfluous <jafo at tummy.com>
tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python