Jeff Laing added the comment:
With all due respect, I think that the 2.7.3 License Page is still being
actively used by people as a reference, and it should be accurate. I agree that
the code developers can't do anything, but the documentation for all releases,
particularly in such a sensitiv
R. David Murray added the comment:
Berkeley DB is no longer part of Python3, so I'm doubtful that this is going to
be addressed. If it is addressed, it would have to be by the PSF rather than
the developers, since the PSF is responsible for licensing issues. If you wish
to pursue this I sug
New submission from Jeff Laing :
As part of an audit of license compliance, I was looking at the terms in the
LICENSE.txt that describe the Berkeley DB product. I had thought this would be
under the standard Berkeley license, but Oracle have added their own zinger.
* 3. Redistributions in any
