Am 17.01.2012 19:02, schrieb Sandro Tosi:
>> I should have given more info, as I wanted the opposite result :)
>> file.next should not link to the next function but to the file.next
>> method. Because Sphinx does not differentiate between
>> meth/func/class/mod roles, :meth:`next` is not resolved
On Mon, Jan 16, 2012 at 16:42, Éric Araujo wrote:
> Hi,
>
> Le 14/01/2012 15:31, Sandro Tosi a écrit :
>>
>> On Sat, Jan 14, 2012 at 04:24, Éric Araujo wrote:
Doc/glossary.rst:520: WARNING: unknown keyword: nonlocal
>>>
>>> That’s a mistake I did in cefe4f38fa0e. This sentence should b
Hi,
Le 14/01/2012 15:31, Sandro Tosi a écrit :
On Sat, Jan 14, 2012 at 04:24, Éric Araujo wrote:
Doc/glossary.rst:520: WARNING: unknown keyword: nonlocal
That’s a mistake I did in cefe4f38fa0e. This sentence should be
removed.
Do you mean revert this whole hunk:
[...]
or just "The :keyword:
On Sat, Jan 14, 2012 at 04:24, Éric Araujo wrote:
> Hi Sandro,
>
> Thanks for getting the ball rolling on this. One style for markup, one
> Sphinx version to code our extensions against and one location for the
> documenting guidelines will make our work a bit easier.
thanks :) I'm happy to help
Hi Sandro,
Thanks for getting the ball rolling on this. One style for markup, one
Sphinx version to code our extensions against and one location for the
documenting guidelines will make our work a bit easier.
During the build process, there are some warnings that I can
understand:
I assume yo
Hi all,
On Sat, Aug 27, 2011 at 07:47, Georg Brandl wrote:
> One of the main reasons for keeping Sphinx compatibility to 0.6.x was to
> enable distributions (like Debian) to build the docs for the Python they ship
> with the version of Sphinx that they ship.
>
> This should now be fine with 1.0.x
Am 23.08.2011 01:09, schrieb Sandro Tosi:
> Hi all,
>
>> Any chance the version of sphinx used to generate the docs on
>> docs.python.org could be updated?
>
> I'd like to discuss this aspect, in particular for the implication it
> has on http://bugs.python.org/issue12409 .
>
> Personally, I do
Wiadomość napisana przez Sandro Tosi w dniu 23 sie 2011, o godz. 01:09:What I want to understand if it's an acceptable change.I see sphinx more as of an internal, building tool, so freezing itit's like saying "don't upgrade gcc" or so.Normally I'd say it's natural for us to specify that for a legac
Hi all,
> Any chance the version of sphinx used to generate the docs on
> docs.python.org could be updated?
I'd like to discuss this aspect, in particular for the implication it
has on http://bugs.python.org/issue12409 .
Personally, I do think it has a value to have the same set of tools to
buil
On Wed, Aug 17, 2011 at 12:08 PM, Chris Withers wrote:
> On 16/08/2011 16:05, Sandro Tosi wrote:
>> I think what's needed first is to run a pilot: take the current 2.7
>> doc,
>
> Where does that live?
> Where are the instructions for building the docs? (dependencies needed, etc)
'make html' in t
On 16/08/2011 16:05, Sandro Tosi wrote:
Hello Chris,
On Wed, Aug 17, 2011 at 00:58, Chris Withers wrote:
Hi All,
Any chance the version of sphinx used to generate the docs on
docs.python.org could be updated?
I think what's needed first is to run a pilot: take the current 2.7
doc,
Where d
Hello Chris,
On Wed, Aug 17, 2011 at 00:58, Chris Withers wrote:
> Hi All,
>
> Any chance the version of sphinx used to generate the docs on
> docs.python.org could be updated?
I think what's needed first is to run a pilot: take the current 2.7
doc, update sphinx and look at what breaks, and eva
Hi All,
Any chance the version of sphinx used to generate the docs on
docs.python.org could be updated?
I'd love to take advantage of the "new format" intersphinx mapping:
http://sphinx.pocoo.org/ext/intersphinx.html#confval-intersphinx_mapping
...but since it looks like docs.python.org uses
13 matches
Mail list logo
