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. Conversely, if it
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? Only
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 their
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 diffs
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
___
[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 cvs2svn)
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
[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
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 get a
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 occurred
[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
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 source
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' in the Lisp
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 take it
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
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
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 problem I
[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
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
19 matches
Mail list logo
