Mercurial > cpython-lru_cache-weakref
diff Doc/python-docs.txt @ 30020:3fe82d57d0d1 legacy-trunk
update the documentation contact address
| author | Fred Drake <fdrake@acm.org> |
|---|---|
| date | Wed, 30 Jul 2003 02:55:28 +0000 |
| parents | 9e7ec2f5a1bd |
| children | 90e0894aec5b f772d3403ca7 |
line wrap: on
line diff
--- a/Doc/python-docs.txt Wed Jul 30 02:55:01 2003 +0000 +++ b/Doc/python-docs.txt Wed Jul 30 02:55:28 2003 +0000 @@ -1,5 +1,5 @@ This message is being sent in response to your message to the Python -documentation maintainers (python-docs@python.org). Your message will +documentation maintainers (docs@python.org). Your message will be handled by a human, but this message serves to answer the most common questions sent to this address. @@ -96,7 +96,7 @@ Start by reading the documentation for XXX. If the documentation doesn't make sense or seems incomplete, please - file a specific bug report to python-docs@python.org (the + file a specific bug report to docs@python.org (the address you sent your question to). Otherwise, you probably sent your question to the wrong place (which does not preclude an answer, if I know it). @@ -124,14 +124,14 @@ http://www.jython.org/ Chances are very good that the person who answers questions - posted to python-docs@python.org doesn't use Jython very often, + posted to docs@python.org doesn't use Jython very often, and won't be able to give you a meaningful answer beyond "Look at the Jython website." Sorry, I don't have *all* the answers! 8. I found a bug in the documentation, who should I tell? If you're reading this, you've found the right address! Send - all documentation bug reports to python-docs@python.org. If + all documentation bug reports to docs@python.org. If you prefer to use a Web-based reporting mechanism, you can use the bug database at http://www.python.org/python-bugs/.
