/usr/local/src/Python-2.4.1/Lib/SimpleXMLRPCServer.py:
raise 'bad method'
/usr/local/src/Python-2.4.1/Demo/classes/bitvec.py:
raise 'FATAL', '(param, l) = %r' % ((param, l),)
/usr/local/src/Python-2.4.1/Lib/plat-mac/FrameWork.py:
raise 'Unsupported in MachoPython'
/usr/local/src/Pyth
Phillip J. Eby wrote:
> At 08:28 PM 8/4/2005 +0200, M.-A. Lemburg wrote:
>
>> BTW, in one of your replies I read that you had a problem with
>> how cvs2svn handles trunk, branches and tags. In reality, this
>> is no problem at all, since Subversion is very good at handling
>> moves within the repo
At 08:28 PM 8/4/2005 +0200, M.-A. Lemburg wrote:
>BTW, in one of your replies I read that you had a problem with
>how cvs2svn handles trunk, branches and tags. In reality, this
>is no problem at all, since Subversion is very good at handling
>moves within the repository: you can easily change the r
Martin v. Löwis wrote:
> M.-A. Lemburg wrote:
>
>>I guess this was a misunderstanding on my part: VA doesn't offer
>>their commercial solution in an ASP-like way. Their product,
>>called SourceForge Enterprise, is a J2EE application which we'd
>>have to install and run. They do mention Subversion
Could someone please make an independent check to verify an issue with
the 342 checkin. The test suite passes but when I run IDLE and open a
new window (using Control-N), it crashes and burns.
The problem does not occur just before the checkin:
cvs up -D "2005-08-01 18:00"
But emerges immedia
M.-A. Lemburg wrote:
> I guess this was a misunderstanding on my part: VA doesn't offer
> their commercial solution in an ASP-like way. Their product,
> called SourceForge Enterprise, is a J2EE application which we'd
> have to install and run. They do mention Subversion as being
> supported by the
In general the PEP looks really good now!
On 8/4/05, Willem Broekema <[EMAIL PROTECTED]> wrote:
> On 8/4/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > OK, once the cron job comes around and is run,
> > http://www.python.org/peps/pep-0348.html will not be a 404 but be the
> > latest version of th
>+-- NamespaceError (rename of NameError)
>+-- UnboundFreeError (new)
>+-- UnboundGlobalError (new)
>+-- UnboundLocalError
>
What are these new exceptions for? Under what circumstances are they
raised? Why is this necessary or an improvement?
> Rename
On 8/4/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> OK, once the cron job comes around and is run,
> http://www.python.org/peps/pep-0348.html will not be a 404 but be the
> latest version of the PEP.
Currently, when the "recursion limit" is reached, a RuntimeError is
raised. RuntimeError is in th
On Aug 4, 2005, at 7:03 AM, Nick Coghlan wrote:
> Additionally, consider that a hypothetical ThreadExit exception
> (used to
> terminate a thread semi-gracefully) would also clearly belong under
> ControlFlowException. That is, just because something is
> asynchronous with
> respect to the curr
Since I forgot to mention it in the last couple of messages - this version
looks very good. The transition strategy section makes it a lot more meaningful.
Brett Cannon wrote (in the PEP):
> Renamed Exceptions
>
> Renamed exceptions will directly subclass the new names. When the old
> exceptions
Brett Cannon wrote (in the PEP):
> KeyboardInterrupt inheriting from ControlFlowException
>
> KeyboardInterrupt has been a contentious point within this hierarchy. Some
> view the exception as more control flow being caused by the user. But with
> its asynchronous cause thanks to the user being ab
Nick Coghlan wrote:
> If/when you add a "Getting there from here" section, it would be worth noting
> that there are a few basic strategies to be applied:
Eh, never mind. It's already there ;)
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
-
Brett Cannon wrote:
> OK, once the cron job comes around and is run,
> http://www.python.org/peps/pep-0348.html will not be a 404 but be the
> latest version of the PEP.
>
> Differences since my last public version is that it has
> BaseException/Exception as the naming hierarchy, Warning inherits
Martin v. Löwis wrote:
> M.-A. Lemburg wrote:
>
>>>I haven't received any offers to make a qualified statement. I only
>>>know that I would oppose an approach to ask somebody but our
>>>volunteers to do it for free, and I also know that I don't want to
>>>spend my time researching commercial alter
15 matches
Mail list logo
