I actually almost asked for that to be changed to a
PendingDeprecationWarning when it was first added - Benjamin, do you
mind if I downgrade this warning to a pending one post rc2?
I'm not sure what that would buy us. For the use case I mentioned it
would be just as annoying to get a
On Sun, 14 Jun 2009 10:40:53 am Greg Ewing wrote:
Zooko Wilcox-O'Hearn wrote:
1. Add a st_crtime field which gets populated on filesystems
(Windows, ZFS, Mac) which can do so.
crtime looks rather too similar to ctime for my
liking. People who think that the c in ctime
means creation are
Steven D'Aprano wrote:
On Sun, 14 Jun 2009 10:40:53 am Greg Ewing wrote:
Zooko Wilcox-O'Hearn wrote:
1. Add a st_crtime field which gets populated on filesystems
(Windows, ZFS, Mac) which can do so.
crtime looks rather too similar to ctime for my
liking. People who think that the c in ctime
2009/6/14 Cameron Simpson c...@zip.com.au:
On 14Jun2009 15:16, I wrote:
| Is it possible to access the buffer? I see nothing in the docs.
I've just found getvalue() in IOBase. Forget I said anything.
It seems to be my day for that kind of post:-(
Where are you seeing this? Only BytesIO and
2009/6/13 Nick Coghlan ncogh...@gmail.com:
Hagen Fürstenau wrote:
I guess this is much too late for 3.1, but could we then at least
un-deprecate contextlib.nested for now? As it is, you get a
DeprecationWarning for something like
with contextlib.nested(*my_managers):
without any good way
I have been doing some work to extend Google's Native Client [1] to
support dynamic linking [2]. For those who haven't heard of it,
Native Client is a sandboxing system for running a subset of x86 code.
It is proposed as a way of running native code inside web apps.
One of my aims has been to
Facundo Batista facundobati...@gmail.com wrote:
errpipe_read, errpipe_write = os.pipe()
try:
try:
.
.
.
.
.
.
finally:
os.close(errpipe_write)
.
.
.
finally:
Exception for setting attributes of built-in type differs between
CPython and IronPython. This is not purely theoretical, as
zope.interface tries to set Implements declaration as __implemented__
attribute of built-in type object, and excepts TypeError.
Python 2.6.1
object.flag = True
TypeError:
Seo Sanghyeon wrote:
Exception for setting attributes of built-in type differs between
CPython and IronPython. This is not purely theoretical, as
zope.interface tries to set Implements declaration as __implemented__
attribute of built-in type object, and excepts TypeError.
Python 2.6.1
Seo Sanghyeon wrote:
Exception for setting attributes of built-in type differs between
CPython and IronPython. This is not purely theoretical, as
zope.interface tries to set Implements declaration as __implemented__
attribute of built-in type object, and excepts TypeError.
Python 2.6.1
Wow. I'm impressed.
On Sun, Jun 14, 2009 at 9:09 AM, Mark Seabornm...@mythic-beasts.com wrote:
I have been doing some work to extend Google's Native Client [1] to
support dynamic linking [2]. For those who haven't heard of it,
Native Client is a sandboxing system for running a subset of x86
On Sun, Jun 14, 2009 at 3:42 PM, MRABpyt...@mrabarnett.plus.com wrote:
Seo Sanghyeon wrote:
Exception for setting attributes of built-in type differs between
CPython and IronPython. This is not purely theoretical, as
zope.interface tries to set Implements declaration as __implemented__
Cameron Simpson wrote:
For myself, I'd expect more often to want to see if there's stuff in the
buffer _without_ doing any raw reads at all.
What uses do you have in mind for that?
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
On 14Jun2009 09:21, Benjamin Peterson benja...@python.org wrote:
| 2009/6/14 Cameron Simpson c...@zip.com.au:
| On 14Jun2009 15:16, I wrote:
| | Is it possible to access the buffer? I see nothing in the docs.
|
| I've just found getvalue() in IOBase. Forget I said anything.
| It seems to be
On 15Jun2009 11:48, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
For myself, I'd expect more often to want to see if there's stuff in the
buffer _without_ doing any raw reads at all.
What uses do you have in mind for that?
It seems like whenever I want to do some kind of opportunistic but
FWIW, I think resurrecting contextlib.nested() is a bad idea.
Part of the justification for the new with-statement syntax was
that nested() doesn't have a way to finalize the constructors
if one of them fails. It is a pitfall for the unwary. And now
that we have the new with-statement syntax,
2009/6/14 Raymond Hettinger pyt...@rcn.com:
FWIW, I think resurrecting contextlib.nested() is a bad idea.
Part of the justification for the new with-statement syntax was
that nested() doesn't have a way to finalize the constructors
if one of them fails. It is a pitfall for the unwary. And
17 matches
Mail list logo
