hello,
On Sat, 24 Mar 2007, Jun-ichiro itojun Hagino wrote:
| > i understand your concern. current 4-tuple is direct mapping from
| > struct sockaddr_in6 (which has those two additional members).
|
| note however, you must rewrite DNS resolving from gethostby* to
| get*info
> | > i understand your concern. current 4-tuple is direct mapping from
> | > struct sockaddr_in6 (which has those two additional members).
> |
> | note however, you must rewrite DNS resolving from gethostby* to
> | get*info anyways, so i'm not too sure if the number of tuple members
[Taking the first day of Pesach as vacation gives me time to respond to
some old threads]
On Wed, Mar 14, 2007, Patrick Maupin wrote:
> On 3/14/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>>
>> I detest the name 'flag_format', though - the function doesn't format a
>> flag!
>
> I don't like it t
On Mon, Mar 12, 2007, Patrick Maupin wrote:
>
> Feature: Alternate syntaxes for escape to markup.
>
> The second method is the well-understood ${} syntax. The $ is easy to
> find in a sea of { characters, and the only special handling required
> is that every $ must be doubled.
-0
> The third
I know everybody is busy, but I would appreciate some kind of feedback
from Python developers about the attached extended buffer protocol which
I am proposing for Python 3k.
I am working on the changes to the struct module needed to accomodate
the enhanced syntax.
I'd like to know if I the
