My guess that there was no specific intent -- most likely it occurred
to nobody that the main() functionality was actually useful. I'd say
it's fine to put it back, and then document it (so it won't be removed
again :-).
--Guido
On Wed, Sep 7, 2011 at 7:06 PM, Meador Inge wrote:
> Hi All,
>
> I
Glyph Lefkowitz writes:
> On Sep 7, 2011, at 10:26 AM, Stephen J. Turnbull wrote:
>
> > How about "title"?
>
> >>> 'content-length'.title()
> 'Content-Length'
>
> You might say that the protocol "has" to be case-insensitive so
> this is a silly frill:
Not me, sir. My whole point about
Hi All,
I have been investing some 'tokenize' bugs recently. As a part of
that investigation I was trying to use '-m tokenize', which works
great in 2.x:
[meadori@motherbrain cpython]$ python2.7 -m tokenize test.py
1,0-1,5:NAME'print'
1,6-1,21: STRING '"Hello, World!"'
1,21-1,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/09/11 14:32, Antoine Pitrou wrote:
> If "-j" is used, tests get run in a separate process each, so that
> approach might be an answer.
Antoine, I think this would be the answer. Each test would be a bit
slower, because I would launch a new pyth
On Thu, Sep 8, 2011 at 3:51 AM, Glyph Lefkowitz wrote:
> On Sep 7, 2011, at 10:26 AM, Stephen J. Turnbull wrote:
>
> How about "title"?
>
'content-length'.title()
> 'Content-Length'
> You might say that the protocol "has" to be case-insensitive so this is a
> silly frill: there are definitely
On Sep 7, 2011, at 10:26 AM, Stephen J. Turnbull wrote:
> How about "title"?
>>> 'content-length'.title()
'Content-Length'
You might say that the protocol "has" to be case-insensitive so this is a silly
frill: there are definitely enough case-sensitive crappy bits of network
middleware out the
Antoine Pitrou writes:
> You could also point out UTF-16 or EBCDIC, but I fail to see how that's
> relevant. Do you have problems with ISO 2022 when parsing, say, e-mail
> headers?
Yes, of course! Especially when it's say, packed EUC not encapsulated
in MIME words. I think Mailman now handle
On Wed, Sep 7, 2011 at 6:31 PM, Simon Cross
wrote:
> http://www.google.com/codesearch#search/&q=swapcase%20lang:%5Epython$&type=cs
>
> There are quite a few hits but more people appear to be
> re-implementing it than using it (I haven't gone to the trouble of
> mining the search results to get an
On Tue, Sep 6, 2011 at 10:36 PM, "Martin v. Löwis" wrote:
>> Which applications? I'm not sure the number of applications using
>> str.swapcase gets even as high as ten.
>
> I think this is what people underestimate. I can't name
> applications either - but that doesn't mean they don't exist.
> I'm
On Wed, 07 Sep 2011 11:15:04 +0900
"Stephen J. Turnbull" wrote:
> Antoine Pitrou writes:
>
> > Bytes objects are often used for partly ASCII strings,
>
> All I can say to that phrase is, "urk, ISO 2022 anyone?"
You could also point out UTF-16 or EBCDIC, but I fail to see how that's
relevant. D
On Wed, 07 Sep 2011 13:38:23 +0200
Jesus Cea wrote:
>
> So, the problem is that a) "make test" takes quite a bit of RAM and b)
> the buildbot forks some "big" processes, so the virtual memory needed
> is BIG.
Note that buildbots run "make buildbottest", not "make test".
> So I have two question
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/09/11 07:27, Nick Coghlan wrote:
> It may be the case that with the reduced memory limit, your
> machine may not be able to run concurrent slaves for 2.7, 3.2 and
> 3.x as I believe it does now.
Antoine has changed the buildmaster configuration
12 matches
Mail list logo
