I have never seen a module where the -*- coding -*- is not the same as
the docstring, either. And the greatest number of times I have seen
this is where people are using some company-wide tool, possibly
third-party and possibly to integrate with java code -- to extract
the docstrings, and also ha
On Mar 24, 2006, at 8:32 PM, Edward Loper wrote:
> David Goodger wrote:
>>> In particular, the question is whether I should assume that the
>>> docstring is encoded with the encoding specified by the "-*- coding
>>> -*-" directive at the top of the file.
>>
>> Yes, it's unreasonable. But such cod
David Goodger wrote:
>> In particular, the question is whether I should assume that the
>> docstring is encoded with the encoding specified by the "-*- coding
>> -*-" directive at the top of the file.
>
> I think that although it's the only possible assumption, it's also
> potentially a wrong assu
[Edward Loper]
> I've been working on epydoc, and the question has come up of how I
> should treat non-unicode docstrings that contain non-ascii
> characters. An example of such a file is
> "python2.4/encodings/string_escape.py", whose module docstring
> contains an 'o' with an umlaut.
>
> In part
