Message206635
| Author |
pitrou |
| Recipients |
akira, christian.heimes, docs@python, gudge, janssen, pitrou |
| Date |
2013年12月19日.19:33:29 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1387481605.2306.4.camel@fsol> |
| In-reply-to |
<1387478292.99.0.452020806799.issue19940@psf.upfronthosting.co.za> |
| Content |
Answering to your questions:
> I have created the patch with git. Let me know if it is okay with you.
Yes, it's ok.
Also, please don't copy / paste it. Uploading is enough.
> Doc changes won't effect the code. The tests would not fail.
> How would I check if the doc changes are coming up fine in the
> final version.
The devguide has detailed documentation about how to modify and build
the documentation :)
http://docs.python.org/devguide/documenting.html#building-the-documentation
As for the tests:
1. for this issue you should probably concentrate on test_ssl: to run it
in verbose mode, "./python -m test -v test_ssl"
(please read http://docs.python.org/devguide/runtests.html)
2. you will need to add a new test to test_ssl, to check that this bug
is indeed fixed |
|