That's great. I just read your draft but I have little comments to do
but before let me say that I liked the idea to borrow concepts from E.
I've crossed the E's path in the beginning of this year and I found it
a pot of really nice ideas (for promises and capabilities). Here are
my comments about
> Should be faster than an IBAC model since certain calls will not need to
> check the identity of the caller every time.
>
> But I am not worrying about performance, I am worrying about correctness, so
> I did not try to make any performance claims.
Got that.
> Nope. Have not started worrying a
In the BZ2File object of bz2 module the writelines() method does not
check its closed state before doing the actual work so its behavior
it's different from write()'s behavior. See:
from bz2 import BZ2File
f = BZ2File("foo", "w")
f.close()
f.closed
1
f.write("foobar")
Traceback (most recent c
> Always post patches -- that way they can't get lost. *THEN* post to
> python-dev with your analysis and explanation (which you presumably also
> included with the patch), starting with a link to the patch.
Thanks for the hint. This is the link:
http://sourceforge.net/tracker/index.php?func=deta
> I think that this change should be presented at
> http://docs.python.org/dev/whatsnew/whatsnew25.html
It's already listed there: http://docs.python.org/dev/whatsnew/other-lang.html
--
Lawrence
http://www.oluyede.org/blog
___
Python-Dev mailing list
> That was my first thought as well. Unfortunately a quick test shows
> that class Foo(): creates an old style class instead :(
I think that's because until it'll be safe to break things we will
stick with classic by default...
--
Lawrence
http://www.oluyede.org/blog
_
On Wed, Jan 28, 2009 at 4:32 AM, Steve Holden wrote:
> I think that both 3.0 and 2.6 were rushed releases. 2.6 showed it in the
> inclusion (later recognizable as somewhat ill-advised so late in the
> day) of multiprocessing; 3.0 shows it in the very fact that this
> discussion has become necessar
