On 17 August 2016 at 09:56, Victor Stinner wrote:
> 2016-08-17 1:50 GMT+02:00 Guido van Rossum :
>> We could expose the class with a
>> constructor that always fails (the C code could construct instances through
>> a backdoor).
>
> Oh, in fact you cannot create an instance of os.DirEntry, it has n
Paul Moore writes:
> On 16 August 2016 at 16:56, Steve Dower wrote:
> > This discussion is for the developers who insist on using bytes
> > for paths within Python, and the question is, "how do we best
> > represent UTF-16 encoded paths in bytes?"
That's incomplete, AFAICS. (Paul makes this
On Wed, Aug 17, 2016 at 9:35 AM, Stephen J. Turnbull
wrote:
> BTW, why "surrogate pairs"? Does Windows validate surrogates to
> ensure they come in pairs, but not necessarily in the right order (or
> perhaps sometimes they resolve to non-characters such as U+1)?
A program can pass the filesy
Brendan,
The conclusion is that you should just file a bug asking for a working
constructor -- or upload a patch if you want to.
--Guido
On Wed, Aug 17, 2016 at 12:18 AM, Nick Coghlan wrote:
> On 17 August 2016 at 09:56, Victor Stinner
> wrote:
> > 2016-08-17 1:50 GMT+02:00 Guido van Rossum :
On 17Aug2016 0235, Stephen J. Turnbull wrote:
Paul Moore writes:
> On 16 August 2016 at 16:56, Steve Dower wrote:
> > This discussion is for the developers who insist on using bytes
> > for paths within Python, and the question is, "how do we best
> > represent UTF-16 encoded paths in bytes
On 17 August 2016 at 02:06, Chris Barker wrote:
> Just to make sure this is clear, the Pragmatic logic is thus:
>
> * There are more *nix-centric developers in the Python ecosystem than
> Windows-centric (or even Windows-agnostic) developers.
>
> * The bytes path approach works fine on *nix system
On 17Aug2016 0901, Nick Coghlan wrote:
On 17 August 2016 at 02:06, Chris Barker wrote:
So the Solution is to either:
(A) get everyone to use Unicode "properly", which will work on all
platforms (but only on py3.5 and above?)
or
(B) kludge some *nix-compatible support for byte paths into Wi
On 16.08.16 22:35, Brendan Moloney wrote:
I have a bunch of functions that operate on DirEntry objects, typically
doing some sort of filtering
to select the paths I actually want to process. The overwhelming
majority of the time these functions
are going to be operating on DirEntry objects produc
eryk sun writes:
> On Wed, Aug 17, 2016 at 9:35 AM, Stephen J. Turnbull
> wrote:
> > BTW, why "surrogate pairs"? Does Windows validate surrogates to
> > ensure they come in pairs, but not necessarily in the right order (or
> > perhaps sometimes they resolve to non-characters such as U+1)
Steve Dower writes:
> On 17Aug2016 0235, Stephen J. Turnbull wrote:
> > So a full statement is, "How do we best represent Windows file
> > system paths in bytes for interoperability with systems that
> > natively represent paths in bytes?" ("Other systems" refers to
> > both other platforms
10 matches
Mail list logo
