On Sun, Jun 5, 2011 at 11:45 AM, Benjamin Peterson benja...@python.org wrote:
Currently,
def f(*, kw, **kwargs): pass
is valid syntax, but
def f(*args, *, kw): pass
is not.
I don't see any mention of it in the PEP but perhaps there is a good
reason this isn't allowed. It seems to be
-1. I think there should be a Python-oriented introduction to sockets.
You may have complaints about the specific wording of the text, but
please understand that these are probably irrelevant to most
first-time readers of this text. My observation is that people actually
don't read the text
I added the if dir=='cjkencodings': to msi.py, based on tests for other
subdirectories in Lib/tests/. Can you explain me why cjkencodings should not
have a special case? The fix should maybe be ported to 3.2, 3.3 and 2.7.
Victor
Le dimanche 05 juin 2011 11:00:30, martin.v.loewis a écrit :
On Sun, 05 Jun 2011 08:32:38 +0200
Martin v. Löwis mar...@v.loewis.de wrote:
-1. I think there should be a Python-oriented introduction to sockets.
You may have complaints about the specific wording of the text, but
please understand that these are probably irrelevant to most
first-time
I'm not currently reading python-dev, dunno if this has come up before:
- Forwarded message from Michael J. Dinneen m...@cs.auckland.ac.nz -
Date: Sun, 05 Jun 2011 19:33:04 +1200
From: Michael J. Dinneen m...@cs.auckland.ac.nz
To: webmas...@python.org
Subject: gpg keys have problems
2011/6/5 Nick Coghlan ncogh...@gmail.com:
On Sun, Jun 5, 2011 at 11:45 AM, Benjamin Peterson benja...@python.org
wrote:
Currently,
def f(*, kw, **kwargs): pass
is valid syntax, but
def f(*args, *, kw): pass
is not.
I don't see any mention of it in the PEP but perhaps there is a good
On Jun 4, 2011, at 11:32 PM, Martin v. Löwis wrote:
b) telling people to use Twisted or asyncore on the server side
if they are new to sockets is bad advice. People *first* have
to understand sockets, and *then* can use these libraries
and frameworks. Those libraries aren't made to be
On Jun 4, 2011, at 11:32 PM, Martin v. Löwis wrote:
b) telling people to use Twisted or asyncore on the server side
if they are new to sockets is bad advice. People *first* have
to understand sockets, and *then* can use these libraries
and frameworks. Those libraries aren't made to
I'm not sure why the examples are good (for example, modern client
code should probably use create_connection() with a host name, not
connect()).
I disagree. create_connection is an advanced function - you shouldn't
be using it unless you know what it is doing.
Can you explain? I would
First, Twisted doesn't always use the BSD sockets API; the Windows IOCP
reactor, especially, starts off with the socket() function, but things
go off in a different direction pretty quickly from there.
Hmm. Are you saying it doesn't use listen, connect, bind, send, recv?
To me, that's the core
On 5 Jun, 10:35 pm, mar...@v.loewis.de wrote:
First, Twisted doesn't always use the BSD sockets API; the Windows
IOCP
reactor, especially, starts off with the socket() function, but things
go off in a different direction pretty quickly from there.
Hmm. Are you saying it doesn't use listen,
11 matches
Mail list logo
