On Tuesday 09 August 2005 09:05, Greg Wilson wrote:
> I'm working with support from the Python Software Foundation to develop an
> open source course on basic software development skills for people with
> backgrounds in science and engineering. I have a beta version of the
> course notes ready for
[Brett]
> The problem with existing code checking for this situation is that the
> situation itself is not the same as it will be if bare 'except's
> change::
>
> try:
>...
> except:
>...
> except TerminatingException:
>...
>
> has never really been possible before, but will be if
Hi,
I'm working with support from the Python Software Foundation to develop an
open source course on basic software development skills for people with
backgrounds in science and engineering. I have a beta version of the
course notes ready for review, and would like to pull in Python-friendly
peop
Dear all,
Sorry to bring this up again, but I think there is an inconsistency in
PEP 348 in its current formulation.
From PEP: "In Python 2.4, a bare except clause will catch any and all
exceptions. Typically, though, this is not what is truly desired. More
often than not one wants to catch a
[Neil Schemenauer[
> I've been getting:
>
> ssh: connect to host cvs.sourceforge.net port 22: Connection refused
>
> for the past few hours. Their "Site News" doesn't say anything
> about downtime.
A cvs update doesn't work for me either now. I did finish one
sometime before noon (EDT) today,
Neil Schemenauer wrote:
> I've been getting:
>
> ssh: connect to host cvs.sourceforge.net port 22: Connection refused
>
> for the past few hours. Their "Site News" doesn't say anything
> about downtime.
I'm seeing the same.
Martin
___
Python-Dev ma
I've been getting:
ssh: connect to host cvs.sourceforge.net port 22: Connection refused
for the past few hours. Their "Site News" doesn't say anything
about downtime.
Neil
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/ma
On Tue, Aug 09, 2005 at 12:28:08AM -0600, Steven Bethard wrote:
> Raymond Hettinger wrote:
> > If the PEP can't resist the urge to create new intermediate groupings,
> > then start by grepping through tons of Python code to find-out which
> > exceptions are typically caught on the same line. That
On 8/8/05, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> [Brett Cannon]
> > At this point the only
> > changes to the hierarchy are the addition of BaseException and
> > TerminatingException, and the change of inheritnace for
> > KeyboardInterrupt, SystemExit, and NotImplementedError.
>
> Termina
On 8/9/05, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> We could always give the text mode/binary mode distinction in "open" a real
> meaning - text mode deals with character sequences, binary mode deals with
> byte sequences.
I thought that's what I proposed before. I'm still for it.
--
--Guido va
On Mon, 2005-08-08 at 19:29, Tim Peters wrote:
> > Currently with svn you have to manually specify those 9 to be sure to not
> > include the remaining one. With p4 you just say to check-in the whole tree
> > and then remove that one from the list give you in your editor with entering
> > the check
Tim Peters wrote:
>
> I can't think of a Python feature with a higher aggregate
> braincell_burned / benefit ratio than __del__ methods. If P3K retains
> them-- or maybe even before --we should consider taking "the Java
> dodge" on this one. That is, decree that henceforth a __del__ method
> wil
Raymond Hettinger wrote:
> TerminatingException
>
>
> The rationale for adding TerminatingException needs to be developed or
> reconsidered. AFAICT, there hasn't been an exploration of existing code
> bases to determine that there is going to be even minimal use of "except
>
Steven Bethard <[EMAIL PROTECTED]> writes:
> Raymond Hettinger wrote:
>> If the PEP can't resist the urge to create new intermediate groupings,
>> then start by grepping through tons of Python code to find-out which
>> exceptions are typically caught on the same line. That would be a
>> worthwhil
James Y Knight wrote:
> Hum, actually, it somewhat makes sense for the "open" builtin to
> become what is now "codecs.open", for convenience's sake, although it
> does blur the distinction between a byte stream and a character
> stream somewhat. If that happens, I suppose it does actually mak
15 matches
Mail list logo
