Re: IP addresses in docs.

2010-11-13 Thread Gabriel Hurley
> Hmm, I don't agree. They are not 'values' in the Python sense - if I > type 127.0.0.1 at a Python prompt I get a syntax error. They are no more > values than integers and floats (less so, by the above definition), and > we don't put any special markup around numbers. They would become values > if

Re: IP addresses in docs.

2010-11-13 Thread Luke Plant
On Sat, 2010-11-13 at 01:23 -0800, Gabriel Hurley wrote: > IP addresses definitely don't belong in plain text since they're a > value... so that option can be ruled out. Hmm, I don't agree. They are not 'values' in the Python sense - if I type 127.0.0.1 at a Python prompt I get a syntax error. Th

Re: IP addresses in docs.

2010-11-13 Thread Gabriel Hurley
IP addresses definitely don't belong in plain text since they're a value... so that option can be ruled out. Between the other two options, I'm torn: I think that using the ``"some_value"`` notation (quotes inside an inline code block) breaks the visual flow for what's usually an obvious distincti

IP addresses in docs.

2010-11-12 Thread Ɓukasz Rekucki
Hi, While updating a patch for ticket #7735 I noticed that docs are inconsistent about how IP addresses should be written. Some are surrounded with double back quotes (``) and some are plain text[1]. After a quick search I also found a quoted one[2]. Is there a preferred way of writing IP address