[Python-Dev] Weekly Python Patch/Bug Summary

2005-08-02 Thread Kurt B. Kaiser
Patch / Bug Summary ___ Patches : 354 open ( -3) / 2888 closed ( +3) / 3242 total ( +0) Bugs: 909 open (+11) / 5152 closed ( +8) / 6061 total (+19) RFE : 191 open ( +0) / 178 closed ( +0) / 369 total ( +0) Patches Closed __ PEP 342 Generator enhance

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread François Pinard
[Donovan Baarda] > It is true that some well designed/developed software becomes reliable > very quicky. However, it still takes heavy use over time to prove that. There is wisdom in your say! :-) -- François Pinard http://pinard.progiciels-bpi.ca _

Re: [Python-Dev] Syscall Proxying in Python

2005-08-02 Thread Donovan Baarda
On Tue, 2005-08-02 at 11:59, Gabriel Becedillas wrote: > Donovan Baarda wrote: [...] > > Wow... you guys sure did it the hard way. If you had done it at the > > Python level, you would have had a much easier time of both implementing > > and updating it. [...] > Hi, thanks for your reply. > The pro

Re: [Python-Dev] PEP, take 2: Exception Reorganization for Python 3.0

2005-08-02 Thread Phillip J. Eby
At 09:02 PM 8/2/2005 -0400, Raymond Hettinger wrote: >The Py3.0 PEPs are a bit disconcerting. Without 3.0 actively in >development, it is difficult to get the participation, interest, and >seriousness of thought that we apply to the current release. The PEPs >may have the effect of prematurely fi

Re: [Python-Dev] PEP, take 2: Exception Reorganization for Python 3.0

2005-08-02 Thread Raymond Hettinger
The Py3.0 PEPs are a bit disconcerting. Without 3.0 actively in development, it is difficult to get the participation, interest, and seriousness of thought that we apply to the current release. The PEPs may have the effect of prematurely finalizing discussions on something that still has an ether

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread Donovan Baarda
On Tue, 2005-08-02 at 09:06, François Pinard wrote: > [Raymond Hettinger] > > > >http://www.venge.net/monotone/ > > > The current release is 0.21 which suggests that it is not ready for > > primetime. > > It suggests it, yes, and to me as well. On the other hand, there is > a common prejudi

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Stephen J. Turnbull
> "Willem" == Willem Broekema <[EMAIL PROTECTED]> writes: Willem> On 8/2/05, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote: >> I don't see it that way. Rather, "Raisable" is the closest >> equivalent to "serious-condition", and "CriticalException" is >> an intermediate class

[Python-Dev] PEP, take 2: Exception Reorganization for Python 3.0

2005-08-02 Thread Brett Cannon
OK, having taken in all of the suggestions, here is another revision round. I think I still have a place or two I partially ignored people just because there was not a severe uproar and I still think the original idea is good (renaming RuntimeError, for instance). I also added notes on handling t

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread Martin v. Löwis
François Pinard wrote: > So, it might be worth at least a quick look? :-) Certainly not my look - although I'm willing to integrate anything that people contribute into the PEP. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://ma

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread Martin v. Löwis
M.-A. Lemburg wrote: > True, but if we never ask, we'll never know :-) > > My question was: Would asking a professional hosting company > be a reasonable approach ? It would be an option, yes, of course. It's not an approach that *I* would be willing to implement, though. >>From the answers, I ta

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Willem Broekema
On 8/2/05, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote: > I don't see it that way. Rather, "Raisable" is the closest equivalent > to "serious-condition", and "CriticalException" is an intermediate > class that has no counterpart in Lisp usage. That would imply that all raisables are 'serious' i

Re: [Python-Dev] Syscall Proxying in Python

2005-08-02 Thread Gabriel Becedillas
Donovan Baarda wrote: > On Mon, 2005-08-01 at 10:36, Gabriel Becedillas wrote: > >>Hi, >>We embbeded Python 2.0.1 in our product a few years ago and we'd like to >>upgrade to Python 2.4.1. This was not a simple task, because we needed >>to execute syscalls on a remote host. We modified Python's s

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Brett Cannon
On 8/2/05, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > At 08:00 PM 8/2/2005 +1000, Nick Coghlan wrote: [SNIP] > Or maybe we > should just make the primary hierarchy the way we want it to be, and only > cross-link exceptions to StandardError that were previously under > StandardError, i.e.: > >

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread François Pinard
[Raymond Hettinger] > >http://www.venge.net/monotone/ > The current release is 0.21 which suggests that it is not ready for > primetime. It suggests it, yes, and to me as well. On the other hand, there is a common prejudice that something requires many releases, or frequent releases, to be

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Phillip J. Eby
At 10:53 AM 8/2/2005 -0400, James Y Knight wrote: >No... KeyboardInterrupt (just like other asynchronous exceptions) >really should be treated as a critical error. Doing anything other >than killing your process off after receiving it is just inviting >disaster. Because the exception can have occur

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Phillip J. Eby
At 08:00 PM 8/2/2005 +1000, Nick Coghlan wrote: >Python 2.4 Compatible Improved Exception Hierarchy v 0.1 > > >Exception >+-- ControlFlowException (new) > +-- GeneratorExit (new) > +-- StopIteration > +-- SystemExit > +

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Phillip J. Eby
At 04:13 PM 8/2/2005 +0900, Stephen J. Turnbull wrote: >Now, somebody proposed: > >Raisable -+- Exception > +- ... > +- ControlFlowException -+- StopIteration >+- KeyboardInterrupt > >As I wrote above, I see no use for that; I think that's wha

Re: [Python-Dev] __autoinit__ (Was: Proposal: reducing self.x=x; self.y=y; self.z=z boilerplate code)

2005-08-02 Thread Terry Reedy
"falcon" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hello python-list, > > As I Understood, semantic may be next: [snip] This was properly posted to the general Python discussion group/list. Reposted here, to the Python development list/group, it is offtopic. If you did not g

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread James Y Knight
On Jul 31, 2005, at 12:49 PM, Phillip J. Eby wrote: > I think you're ignoring the part where most exception handlers are > already broken. At least adding CriticalException and > ControlFlowException makes it possible to add this: > > try: > ... > except (CriticalException,Con

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread Raymond Hettinger
[François Pinard] > While some say Subversion is the most reasonable avenue nowadays, others > them told me they found something more appealing than Subversion: > >http://www.venge.net/monotone/ The current release is 0.21 which suggests that it is not ready for primetime. Raymond

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread James Y Knight
On Aug 2, 2005, at 12:31 AM, Phillip J. Eby wrote: > If you think that a KeyboardInterrupt is an error, then it's an > indication > that Python's documentation and the current exception class > hierarchy has > failed to educate you sufficiently, and that we *really* need to add a > class like C

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread François Pinard
[Martin von Löwis] > The PEP is only about Subversion. I think anything but Subversion is > ruled out because: > - there is no offer to host that anywhere (for subversion, there is > already svn.python.org) > - there is no support for converting a CVS repository (for subversion, > there is cvs2

[Python-Dev] __autoinit__ (Was: Proposal: reducing self.x=x; self.y=y; self.z=z boilerplate code)

2005-08-02 Thread falcon
Hello python-list, As I Understood, semantic may be next: def qwerty(a,a.i,b,b.i,f.j): pass Would work like: def qwerty(anonymous1,anonymous2,anonymous3,anonymous4,anonymous5): (a,a.i,b,b.i,f.j)=(anonymous1,anonymous2,anonymous3,anonymous4,anonymous5) del anonymous1

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Mark Russell
On Tue, 2005-08-02 at 11:00, Nick Coghlan wrote: > With this hierarchy, the recommended parent class for application errors > becomes Error, ... And presumably Error could also be the recommended exception for quick'n'dirty scripts. Mark Russell ___ P

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread Michael Hudson
Donovan Baarda <[EMAIL PROTECTED]> writes: > This is why I don't bother migrating any existing CVS projects to SVN; > the benefits don't yet outweigh the pain of migrating. I think they do. I was on dialup for a while, and would have _loved_ Python to be using SVN then -- and given how long diff

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread M.-A. Lemburg
Nick Coghlan wrote: > I have a Python 2.5 candidate hierarchy below, which uses dual inheritance to > avoid breaking backward compatibility - any existing except clauses will > catch > all of the exceptions they used to catch. The only new inheritance introduced > is to new exceptions, also avo

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Nick Coghlan
Stephen J. Turnbull wrote: > Now, somebody proposed: > > Raisable -+- Exception > +- ... > +- ControlFlowException -+- StopIteration >+- KeyboardInterrupt > > As I wrote above, I see no use for that The use for it is : try: # do st

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread M.-A. Lemburg
Martin v. Löwis wrote: > M.-A. Lemburg wrote: > > The PSF does have a reasonable budget, so why not use it to > > maintain the infrastructure needed for Python development and > > let a company do the administration of the needed servers and > > the importing of the CSV and tracker items into t

Re: [Python-Dev] PEP: Migrating the Python CVS to Subversion

2005-08-02 Thread Martin v. Löwis
George V. Neville-Neil wrote: > Since Python is Open Source are you looking at Per Force which you can > use for free and seems to be a happy medium between something like CVS > and something horrific like Clear Case? No. The PEP is only about Subversion. Why should we be looking at Per Force? Onl

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Stephen J. Turnbull
> "Phillip" == Phillip J Eby <[EMAIL PROTECTED]> writes: Phillip> You just said, "Unhandled, KeyboardInterrupt means..." Phillip> If the program doesn't *want* to handle Phillip> KeyboardInterrupt, then it obviously *isn't* critical, Phillip> because it doesn't care. Conversel