The purpose of .pyc is to optmize python. With your proposed change, the
number of syscalls is doubled (open, read, close) and you add extra work
(compute hash) when .pyc is used.
If your filesystem works correctly, you should not have to bother.
Victor
Le 15 août 2016 01:06, "Xavier Combelle"
But we do not care if the experimental animal dies, that is the point of
doing the experiment.
I registered at Discuss and kina like it. Then tried to create a new thread
and my Android keyboard shows over the fields. Discuss As it is now doesnt
work for mobile.
14 sie 2016 9:35 PM "Arek Bulski"
For those talking abstract points, here is a screenshot of GitHub. Works
like a charm on mobile.
https://s3.postimg.org/e30lc3tk3/Screenshot_2016_08_15_13_00_59_com_browser_inter.png
15 sie 2016 10:34 AM "Arek Bulski" napisał(a):
> But we do not care if the experimental animal dies, that is the
One person saying "this thread doesnt belong here" doesnt make it so. I
have met too often in my life with a situation where people were chasing
others away because they simply didnt like the particular topic. This
thread still Has its participants. You are replying on it As well. And
until Discuss
I guess I'm not sure what your question is then.
Using text internally is of course the best way to deal with it. But for those
who insist on using bytes, this change at least makes Windows a feasible target
without requiring manual encoding/decoding at every boundary.
Top-posted from my Window
On Mon, Aug 15, 2016, at 09:23, Steve Dower wrote:
> I guess I'm not sure what your question is then.
>
> Using text internally is of course the best way to deal with it. But for
> those who insist on using bytes, this change at least makes Windows a
> feasible target without requiring manual enco
I'm still not sure we're talking about the same thing right now.
For `open(path_as_bytes).read()`, are we talking about the way path_as_bytes is
passed to the file system? Or the codec used to decide the returned string?
Top-posted from my Windows Phone
-Original Message-
From: "Random8
On Mon, Aug 15, 2016, at 12:35, Steve Dower wrote:
> I'm still not sure we're talking about the same thing right now.
>
> For `open(path_as_bytes).read()`, are we talking about the way
> path_as_bytes is passed to the file system? Or the codec used to decide
> the returned string?
We are talking
On 15Aug2016 0954, Random832 wrote:
On Mon, Aug 15, 2016, at 12:35, Steve Dower wrote:
I'm still not sure we're talking about the same thing right now.
For `open(path_as_bytes).read()`, are we talking about the way
path_as_bytes is passed to the file system? Or the codec used to decide
the retu
On 15Aug2016 1126, Steve Dower wrote:
My proposal is to remove all use of the *A APIs and only use the *W
APIs. That completely removes the (already deprecated) use of bytes as
paths. I then propose to change the (unused on Windows)
sys.getfsdefaultencoding() to 'utf-8' and handle bytes being pas
On Aug 14, 2016, at 02:01 PM, Chris Angelico wrote:
>The biggest problem I'm seeing is with digests. Can that feature be
>flagged off as "DO NOT USE THIS UNLESS YOU KNOW WHAT YOU ARE ASKING
>FOR"? So many people seem to select digest mode, then get extremely
>confused by it.
Yes, we can turn off
On Mon, Aug 15, 2016 at 6:26 PM, Steve Dower wrote:
>
> (Frankly I don't mind what encoding we use, and I'd be quite happy to force
> bytes
> paths to be UTF-16-LE encoded, which would also round-trip invalid surrogate
> pairs. But that would prevent basic manipulation which seems to be a higher
> Given that, I'm proposing adding support for using byte strings encoded with
> UTF-8 in file system functions on Windows. This allows Python users to omit
> switching code like:
>
> if os.name == 'nt':
>f = os.stat(os.listdir('.')[-1])
> else:
>f = os.stat(os.listdir(b'.')[-1])
REALLY?
On 15Aug2016 1819, eryk sun wrote:
On Mon, Aug 15, 2016 at 6:26 PM, Steve Dower wrote:
(Frankly I don't mind what encoding we use, and I'd be quite happy to force
bytes
paths to be UTF-16-LE encoded, which would also round-trip invalid surrogate
pairs. But that would prevent basic manipulatio
On 16 August 2016 at 11:34, Chris Barker - NOAA Federal
wrote:
>> Given that, I'm proposing adding support for using byte strings encoded with
>> UTF-8 in file system functions on Windows. This allows Python users to omit
>> switching code like:
>>
>> if os.name == 'nt':
>>f = os.stat(os.lis
>> On Mon, Aug 15, 2016 at 6:26 PM, Steve Dower
>> wrote:
>
> and using the *W APIs exclusively is the right way to go.
My proposal was to use the wide-character APIs, but transcoding CP_ACP
without best-fit characters and raising a warning whenever the default
character is used (e.g. substitutin
16 matches
Mail list logo
