On Tue, 28 Aug 2018 at 07:56, Nick Coghlan wrote:
>
> On Mon., 20 Aug. 2018, 11:54 pm Paul Moore, wrote:
>>
>> My assumption is that the intent is that *all* strings, whether
>> arguments or return values, must be Unicode.
>
> Handling bytes paths correctly cross-platform is a pain, so I think
On Mon., 20 Aug. 2018, 11:54 pm Paul Moore, wrote:
>
> My assumption is that the intent is that *all* strings, whether
> arguments or return values, must be Unicode.
>
Handling bytes paths correctly cross-platform is a pain, so I think
requiring frontends to always pass in Unicode makes sense.
On Mon, 20 Aug 2018 at 18:54, Thomas Kluyver wrote:
>
> On Mon, Aug 20, 2018, at 2:52 PM, Paul Moore wrote:
> > The various hooks take directory paths as arguments, and typically
> > return a filename (e.g., build_wheel). The returned filename is always
> > explicitly noted as being *a unicode
On Mon, Aug 20, 2018, at 2:52 PM, Paul Moore wrote:
> The various hooks take directory paths as arguments, and typically
> return a filename (e.g., build_wheel). The returned filename is always
> explicitly noted as being *a unicode string*. However, argumnents
> (metadata_directory in
