Inky 788 writes:
> Could you please provide brief instructions on exactly how to go about
> creating a suitable patch file? I mean, starting from the beginning
> (as in, "check out code from {here} using {this command}", "cd to
> {this} directory", "edit the file in place", "run {this} command to
Inky 788 wrote:
> On Jul 22, 7:15 am, Tim Golden wrote:
>> Mark du Preez wrote:
>>> Hi
>>> Can anyone tell me where to go to suggest changes to the Python
>>> documentation?
>> Drop an entry in the tracker:
>>
>> http://bugs.python.org
>>
>> Patches are always welcome,
>
> Could you please provi
Diez B. Roggisch wrote:
Mark du Preez wrote:
Hi
Can anyone tell me where to go to suggest changes to the Python
documentation?
Thanks.
http://docs.python.org/ has a "bugs"-section that leads to
http://docs.python.org/bugs.html
You can file doc-bugs in the tracker, and check if they are al
On Jul 22, 7:15 am, Tim Golden wrote:
> Mark du Preez wrote:
> > Hi
>
> > Can anyone tell me where to go to suggest changes to the Python
> > documentation?
>
> Drop an entry in the tracker:
>
> http://bugs.python.org
>
> Patches are always welcome,
Could you please provide brief instructions on
Mark du Preez wrote:
> Hi
>
> Can anyone tell me where to go to suggest changes to the Python
> documentation?
>
> Thanks.
http://docs.python.org/ has a "bugs"-section that leads to
http://docs.python.org/bugs.html
You can file doc-bugs in the tracker, and check if they are already fixed in
t
Mark du Preez wrote:
Hi
Can anyone tell me where to go to suggest changes to the Python
documentation?
Drop an entry in the tracker:
http://bugs.python.org
Patches are always welcome, or at least suggested wording rather
than vague "I don't think it should say that" -- although that's
bett
