On Saturday 29 October 2005 15:40, martin.v.loewis(a)python.org wrote:
> Author: martin.v.loewis
> Date: Sat Oct 29 21:40:21 2005
> New Revision: 41352
> python/trunk/ (props changed)
> Add *.pyc to svn:ignore.
> Add libpython*.a to .cvsignore and svn:ignore.
Shouldn't we simply remove the .cvsignore files? Subversion doesn't use them,
so they'll just end up getting out of sync with the svn:ignore properties.
Fred L. Drake, Jr. <fdrake at acm.org>
The Python source code repository is now converted to subversion;
please feel free to start checking out new sandboxes. For a few
days, this installation probably still needs to be considered in
testing. If there are no serious problems found by next Monday,
I would consider conversion of the data complete. The CVS repository
will be kept available read-only for a while longer, so you can
easily forward any patches you may have.
Most of you are probably interested in checking out one of these
The anonymous read-only equivalents of these are
As mentioned before, in addition to "plain" http/WebDAV,
viewcvs is available at
There are some more things left to be done, such as updating
the developer documentation. I'll start working on that soon,
but contributions are welcome.
Once the cron job works it magic, the updated PEP 343 should be available on
As far as I am aware, there aren't any more open issues, so it is once again
ready for BDFL pronouncement.
I also tinkered with the example naming a bit, and added a new example for the
"nested" context manager (it turns out there *were* mistakes in the last
version I posted here - I had the deque method name wrong, and I wasn't
invoking __context__ correctly on the nested contexts).
P.S. My availability will be sketchy for the rest of this weekend, then
nonexistent until next weekend, so don't be surprised if I don't respond to
messages before then.
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
Well, I am at it again, but this time Guido is a co-conspirator. We
wrote a PEP that introduces BaseException and moves KeyboardInterrupt
and SystemExit. Even if you followed the discussion for PEP 348 you
should read the PEP since I am sure there will be something that
someone doesn't like, such as the transition plan or how I didn't use
British English throughout. =)
Anyway, as soon as the cron job posts the PEP to the web site (already
checked into the new svn repository) have a read and start expounding
about how wonderful it is and that there is no qualms with it
I'm trying to make a module to support inotify (linux). I put together a
module using boost::python. Problem is, inotify uses a file descriptor.
If I call python os.fdopen on it, I get an error:
Python 2.4.1 (#1, May 16 2005, 15:15:14)
[GCC 4.0.0 20050512 (Red Hat 4.0.0-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from inotify import *
>>> import os
>>> os.fdopen (i.fileno())
Traceback (most recent call last):
File "<stdin>", line 1, in ?
IOError: [Errno 21] Is a directory
Any ideas? I'd rather not have to trace through python if I could avoid it
(I don't even have source installed here).
> I find "AttributeError: __exit__" just as informative.
Eric Nieuwland responds:
> I see. Then why don't we unify *Error into Error?
> Just read the message and know what it means.
> And we could then drop the burden of exception classes and only use the
> A sense of deja-vu comes over me somehow ;-)
The answer (and there _IS_ an answer) is that using different exception
types allows the user some flexibility in CATCHING the exceptions. The
discussion you have been following obscures that point somewhat because
there's little meaningful difference between TypeError and
AttributeError (at least in well-written code that doesn't have
unnecessary typechecks in it).
If there were a significant difference between TypeError and
AttributeError then Nick and Guido would have immediately chosen the
appropriate error type based on functionality rather than style, and
there wouldn't have been any need for discussion.
Oh yeah, and you can also put extra info into an exception object
besides just the error message. (We don't do that as often as we
should... it's a powerful technique.)
-- Michael Chermside
I m a student of Computer Science Dept.
University Of Pune.(M.S.) (India). We are learning
python as a course for our semester. Found its not
only use full but heart touching laguage.
Sir , I have found that the python is going
to have new feature, of "? " operator, same as in C
Kindly provide me with the information that
in version of python we will be able to find that
feature and when it is about to realse.
Considering your best of sympathetic
consideration. Hoping for early response.
Mr. Lucky R. Wankhede
Dept. Of Comp.
University of Pune,
Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.com