>> Sure. But (again): you don't need to have the mappings at all for
>> what you want to achieve. So there is no point in downloading them
>
> Sigh. No, I don't. But, if I want to be able to merge anything
> back into the main Python source, it is a VERY good idea to use the
> existing mechanism
=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= <[EMAIL PROTECTED]> wrote:
>
> Sure. But (again): you don't need to have the mappings at all for
> what you want to achieve. So there is no point in downloading them
Sigh. No, I don't. But, if I want to be able to merge anything
back into the main Pytho
>> Ah, the makefile. I don't think you use it create the Unicode database.
>>
>> It's only good for generating the codecs (Lib/encodings)
>
> Yes, but it DOES attempt to download the mappings, and is the ONLY
> script which attempts to do so.
Sure. But (again): you don't need to have the mappings
Nick Maclaren wrote:
>> Ah, the makefile. I don't think you use it create the Unicode database.
>>
>> It's only good for generating the codecs (Lib/encodings)
>
> Yes, but it DOES attempt to download the mappings, and is the ONLY
> script which attempts to do so.
Of course it does. The Tools/unic
=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= <[EMAIL PROTECTED]> wrote:
>
> > I think that you will find that you are using a non-standard
> > environment and set of Python sources.
>
> Please trust me that I didn't. See below.
I always trust people as much as I trust myself, but I do tend to
check
