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 belopolsky
Recipients amaury.forgeotdarc, belopolsky, gvanrossum, loewis, schmir, vstinner
Date 2010-07-29.15:52:06
SpamBayes Score 0.0025675679
Marked as misclassified No
Message-id <>
In-reply-to <>
On Wed, Jul 28, 2010 at 11:22 PM, Guido van Rossum
<> wrote:
> What about the licensing? That look like the BSD license *with*
> advertising clause...

I am not a lawyer and I am not intimately familiar with PSF policies,
but this license does not look too dissimilar to the profile module

# Permission to use, copy, modify, and distribute this Python software
# and its associated documentation for any purpose (subject to the
# restriction in the following sentence) without fee is hereby
# provided that the above copyright notice appears in all copies, and
# that both that copyright notice and this permission notice appear in
# supporting documentation, ...

Actually, I wonder if pydoc profile is technically in violation of the
InfoSeek license.  More likely, however, is that the license text in
the source file is not authoritative and PSF has a more permissive
license to this code.

Skip, can you clarify where the strftime code in your patch came from?
 In your first post you said that it came from Tcl, so it may have
ActiveState copyright on at least portions of it.

On the other hand, unless strftime code is already published under an
acceptable license, I think rewriting this code from scratch would be
easier than tracking down the owners and asking them to contribute it
to python.
Date User Action Args
2010-07-29 15:53:03belopolskysetrecipients: + belopolsky, gvanrossum, loewis, amaury.forgeotdarc, vstinner, schmir
2010-07-29 15:52:07belopolskylinkissue3173 messages
2010-07-29 15:52:06belopolskycreate