This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author fdrake
Recipients
Date 2004-11-11.06:33:01
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=3066

I'll note that the "Macintosh Library Modules" document
deals with this sort of issue for the Mac (though it may be
out of date for Mac OS X; not sure).  The first chapter is
an introduction to using Python on the Mac, and the
remaining chapters provide module reference documentation.

What's needed is something like the first chapter of that
for Unix and Windows.  I'm not sure where it should go,
though; I don't want that material in the main library
reference.

This almost makes me want three platform-specific documents,
one for Windows, one for Unix, and the existing Mac OS
document, each containing the relevant "Using Python on ..."
chapter, followed by chapters containing platform-specific
modules.  Modules that apply to two or more of the platforms
would continue to be documented in the main library
reference.  The distutils modules are already documented in
the distutils documentation as well.  This should be fine
since the "global" module index is the normal general entry
point anyway.
History
Date User Action Args
2007-08-23 13:56:45adminlinkissue469773 messages
2007-08-23 13:56:45admincreate