Hi all,
I created a patch on 2007-08-15:
http://bugs.python.org/issue1775025
I wonder, will it just stay in patches unnoticed until it has its very
own associated bug report to keep it company?
Thanks,
Graham
___
Python-Dev mailing list
Python-Dev@py
On 18 Jan 2008, 06:42:26, Steve Holden wrote:
> [EMAIL PROTECTED] wrote:
> > Thank you very much for the quick reply.
> >
> > I believe we have to close the file in order be able to read it in - in this
> > case to feed a unittest. I actually tried to read it in before closing it,
> > but (as I s
Are we scraping the __bottom__ of the English language __barrel__?
Perhaps someone here can draw some inspiration from __monty__ python's
flying __circus__. It would be nice to have a name with a pythonic
__ground__.
Unfortunately that show is not my __staple__ entertainment, and although
I hav
This is an interesting thread, here is my 1c :-)
Unless one is feeling chronologically challenged, it is always the
__last__ layer looked in as Christian Heimes described, so maybe
__lastns__ or __latter__, or even __zns__.
Perhaps __final__ or __finalns__ sounds too similar to "finally:".
How a
On 12 Nov 2007, 03:24:34, Jan Claeys wrote:
>
> Op zondag 11-11-2007 om 17:19 uur [tijdzone -0800], schreef Brett
> Cannon:
> > On Nov 11, 2007 4:00 PM, Graham Horler <[EMAIL PROTECTED]> wrote:
> > > I have been developing in Python since 1.5, and now have to
I have been developing in Python since 1.5, and now have to support 2.1
as a minimum version. I do like to keep my code runnable on newer
versions however, and am considering the feasability of forward
compatibility with Python 3.0.
I also notice the Leo[1] project could use some assistance with
I would be inclined to move gcc to gcc-real (for example), and create a script
called gcc which dumps all environment variables, and command-line arguments
and a time-stamp to /tmp/gcc., e.g.:
#!/bin/sh
FN=/tmp/gcc.$$
echo -n "date=" > $FN
date '+%Y/%m/%d %H:%M:%S.%N' >> $FN
echo -n "cmdline=" >>
On 27 Sep 2007, 21:23:58, Brett Cannon wrote:
> Should OSError and IOError become aliases to EnvironmentError? I
> assume WindowsError and VMSError will just directly subclass which
> ever exception sticks around.
>
> And should we bother with a PendingDeprecationWarning for IOError or
> OSError?
+1 for mutual authentication, I would use this.
Can the TLS handshake be made to respect timeouts on sockets, or would
this require changes deep inside OpenSSL?
Graham
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/list
