The header of the file seems to imply that the module
is licensed
separately from the standard Python license:


# subprocess - Subprocesses with accessible I/O streams
#
# For more information about this module, see PEP 324.
#
# Copyright (c) 2003-2004 by Peter Astrand
<astrand@lysator.liu.se>
#
# By obtaining, using, and/or copying this software
and/or its
# associated documentation, you agree that you have
read, understood,
# and will comply with the following terms and conditions:
#
# Permission to use, copy, modify, and distribute this
software and
# its associated documentation for any purpose and
without fee is
# hereby granted, provided that the above copyright
notice appears in
# all copies, and that both that copyright notice and
this permission
# notice appear in supporting documentation, and that
the name of the
# author not be used in advertising or publicity
pertaining to
# distribution of the software without specific,
written prior
# permission.
#
# THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE,
# INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS.
# IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
SPECIAL, INDIRECT OR
# CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS
# OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT,
# NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION
# WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Logged In: YES 
user_id=344921

How should the license header look like, then? Basically,
I've used xmlrpclib.py as an example. Many other modules
have no license header at all, but this might be a problem
when subprocess.py is distributed separately from Python. Or?

Logged In: YES 
user_id=357491

Have you signed a contributor agreement yet, Peter?  If you have your 
code has already been relicensed to the PSF under the PSF license.  If 
you haven't you will be asked to eventually and that will retroactively 
relicense your code over to the PSF, essentially negating all of this pre-
existing license.

You can replace the above license if you have signed the contributor 
agreement with:

Copyright 2005 by Peter Åstrand.
Licensed to PSF under a Contributor Agreement

Assuming I am right.  =)  You can double-check by emailing 
psf@python.org or ask at PyCon if you are attending.

Logged In: YES 
user_id=344921

>Have you signed a contributor agreement yet, Peter? 

Yes. 

>You can replace the above license if you have signed the
>contributor agreement with:
>
>Copyright 2005 by Peter Åstrand.
>Licensed to PSF under a Contributor Agreement

I guess this will work good when subprocess.py is
distributed with the Python distribution, but subprocess.py
is also distributed separately, as an addon to Python
2.2/2.3. In this case, it feels better to include the
license itself. 

Logged In: YES 
user_id=344921

Fixed in revision 1.8.2.5 (2.4 branch) and 1.21 (HEAD).