On Wed, 13 Mar 2019 at 08:13, eryk sun wrote:
>
> On 3/12/19, Paul Moore wrote:
> >
> > Do you care about case sensitivity (for example, is it important to you
> > whether filenames "foo" and "FOO" map to the same file or not on
> > Linux, given that they do on Windows)?
>
> That's no longer a gi
On 3/12/19, Paul Moore wrote:
>
> Do you care about case sensitivity (for example, is it important to you
> whether filenames "foo" and "FOO" map to the same file or not on
> Linux, given that they do on Windows)?
That's no longer a given in Windows, since NTFS in Windows 10 supports
case-sensiti
On Tue, 12 Mar 2019 at 14:54, Malcolm Greene wrote:
>
> Looking for best practice technique for converting Windows style paths to
> Linux paths. Is there an os function or pathlib method that I'm missing or is
> it some combination of replacing Windows path separators with Linux path
> separato
On Tue, Mar 12, 2019, Malcolm Greene wrote:
>Looking for best practice technique for converting Windows style paths to
>Linux paths. Is there an os function or pathlib method that I'm missing or
>is it some combination of replacing Windows path separators with Linux path
>separators plus some othe
On 12/03/2019 15.51, Malcolm Greene wrote:
> Looking for best practice technique for converting Windows style paths to
> Linux paths. Is there an os function or pathlib method that I'm missing or is
> it some combination of replacing Windows path separators with Linux path
> separators plus some
Looking for best practice technique for converting Windows style paths to Linux
paths. Is there an os function or pathlib method that I'm missing or is it some
combination of replacing Windows path separators with Linux path separators
plus some other platform specific logic?
Thank you,
Malcolm
