Re: [Python-Dev] casefolding in pathlib (PEP 428)
On 12/04/2013 22:15, Larry Hastings wrote:
On 04/12/2013 10:05 AM, Guido van Rossum wrote:
On Fri, Apr 12, 2013 at 1:39 AM, Antoine Pitrou
wrote:
I think we want glob("*.py") to find
"SETUP.PY" under Windows. Anything else will probably be surprising to
users of that platform.
Yeah, I suppose so. But there are more crazy details. E.g. IIRC
Windows silently ignores trailing dots in filenames. Do we want
"*.py." to match SETUP.PY then?
Someone who is fresher than I am at Windows programming should answer
this, but AFAICT Win32 provides no API that will tell you if a
particular filename / volume is case sensitive.
I don't have web access at the moment to check but IIRC the
GetVolumeInformation call does return an indicator of whether the volume
is case-sensitive via the VOLUME_FLAG flag enum. At least, it claims to:
I don't have access to a case-sensitive filesystem to check whether it's
lying or not.
TJG
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython: Issue #17693: CJK encoders now use the new Unicode API (PEP 393)
On Sun, Apr 14, 2013 at 10:06 AM, victor.stinner wrote: > http://hg.python.org/cpython/rev/d621bdaed7c3 > changeset: 83317:d621bdaed7c3 > user:Victor Stinner > date:Sun Apr 14 02:06:32 2013 +0200 > summary: > Issue #17693: CJK encoders now use the new Unicode API (PEP 393) I'm going to run with the wild theory that there's a reference link in here somewhere... :) results for 0ee785c9d1b4 on branch "default" -- -- test_unittest leaked [-1, 2, 1] memory blocks, sum=2 test_codecencodings_cn leaked [16133, 16133, 16133] references, sum=48399 test_codecencodings_cn leaked [28992, 28994, 28994] memory blocks, sum=86980 test_codecencodings_hk leaked [378, 378, 378] references, sum=1134 test_codecencodings_hk leaked [414, 416, 416] memory blocks, sum=1246 test_codecencodings_iso2022 leaked [13861, 13861, 13861] references, sum=41583 test_codecencodings_iso2022 leaked [25698, 25700, 25700] memory blocks, sum=77098 test_codecencodings_jp leaked [39322, 39322, 39322] references, sum=117966 test_codecencodings_jp leaked [71335, 71337, 71337] memory blocks, sum=214009 test_codecencodings_kr leaked [9033, 9033, 9033] references, sum=27099 test_codecencodings_kr leaked [15844, 15846, 15846] memory blocks, sum=47536 test_codecencodings_tw leaked [3879, 3879, 3879] references, sum=11637 test_codecencodings_tw leaked [6562, 6564, 6564] memory blocks, sum=19690 test_codecs leaked [1296, 1296, 1296] references, sum=3888 test_codecs leaked [384, 386, 386] memory blocks, sum=1156 test_multibytecodec leaked [44, 44, 44] references, sum=132 test_multibytecodec leaked [21, 23, 23] memory blocks, sum=67 test_traceback leaked [2, 2, 2] references, sum=6 test_traceback leaked [4, 6, 6] memory blocks, sum=16 Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython: Issue #17693: CJK encoders now use the new Unicode API (PEP 393)
On Sun, Apr 14, 2013 at 9:49 PM, Nick Coghlan wrote: > On Sun, Apr 14, 2013 at 10:06 AM, victor.stinner > wrote: >> http://hg.python.org/cpython/rev/d621bdaed7c3 >> changeset: 83317:d621bdaed7c3 >> user:Victor Stinner >> date:Sun Apr 14 02:06:32 2013 +0200 >> summary: >> Issue #17693: CJK encoders now use the new Unicode API (PEP 393) > > I'm going to run with the wild theory that there's a reference link in > here somewhere... :) Or, perhaps even a reference *leak*! I can't even blame autocorrect for that one, since I typed it at my desk on a real keyboard :) Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython: Issue #17693: CJK encoders now use the new Unicode API (PEP 393)
Hi, 2013/4/14 Nick Coghlan : > On Sun, Apr 14, 2013 at 10:06 AM, victor.stinner > wrote: >> http://hg.python.org/cpython/rev/d621bdaed7c3 >> changeset: 83317:d621bdaed7c3 >> user:Victor Stinner >> date:Sun Apr 14 02:06:32 2013 +0200 >> summary: >> Issue #17693: CJK encoders now use the new Unicode API (PEP 393) > > I'm going to run with the wild theory that there's a reference link in > here somewhere... :) > > results for 0ee785c9d1b4 on branch "default" > -- > -- > > test_codecencodings_cn leaked [16133, 16133, 16133] references, sum=48399 > test_codecencodings_cn leaked [28992, 28994, 28994] memory blocks, sum=86980 > ... Oh thanks for the report. My laptop is too slow to run the test suite using -R. It should be fixed by: New changeset ffd4b72f7f95 by Victor Stinner in branch 'default': Issue #17693: Fix memory/reference leaks http://hg.python.org/cpython/rev/ffd4b72f7f95 Victor ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Deciding against the CLA
On 13/04/13 20:30, Ben Finney wrote: "Stephen J. Turnbull" writes: Mark Lawrence writes: > People already use the bug tracker as an excuse not to contribute, > wouldn't this requirement make the situation worse? A failure to sign the CLA is already a decision not to contribute to the distribution As someone who cannot in good faith sign the CLA, that characterisation is far from accurate: I would very much like to contribute to the Python distribution, and so have not decided as you describe. Could you explain, briefly, why you cannot sign the CLA? -- Steven ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Deciding against the CLA
Ben Finney writes: > "Stephen J. Turnbull" writes: > > > Mark Lawrence writes: > > > > > People already use the bug tracker as an excuse not to > > > contribute, wouldn't this requirement make the situation > > > worse? > > > > A failure to sign the CLA is already a decision not to contribute > > to the distribution > > As someone who cannot in good faith sign the CLA, that > characterisation is far from accurate: I would very much like to > contribute to the Python distribution, and so have not decided as > you describe. > > Rather, I leave the matter of contribution undecided, Whatever. In fact, the consequence of your failure to sign the CLA is that your code doesn't get distributed with any of the current Python releases, is that correct? Back in context, I don't see how placing a reminder to sign the CLA on the page makes your decision at that instant harder. I suppose it might deter you from submitting code that by policy shouldn't be included in the distribution, but might be useful to third parties. Whether such deterrence is a good thing or a bad thing would depend on how likely it was to be independently invented by some who is willing to contribute code, and whether you would try to enforce your copyright in the event that it resembled your code (in which case there would be an obvious case for infringement, with the burden of proof on the individual who is willing to sign the CLA). (By the way, what is your problem of conscience with the PSF CLA? Are you afraid that the PSF's obligation to use an "open source license" is not enforceable? You don't like the choice of Initial Licenses? Something else?) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
