On Mon, Apr 7, 2008 at 11:58 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> We have a way to raise an exception in a thread asynchronously, *but*
> we don't have a way to interrupt either system calls or blocked lock
> acquisitions. I suppose that system calls can be made interruptable
> with
We have a way to raise an exception in a thread asynchronously, *but*
we don't have a way to interrupt either system calls or blocked lock
acquisitions. I suppose that system calls can be made interruptable
with suitable tweaking of various signal-related settings (at least on
Unix -- and I expect
On Mon, Apr 7, 2008 at 7:40 PM, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
>
> > Maybe it should be a forked subprocess then, if it doesn't touch
> > anything shared?
>
> It might be taking and returning large data structures
> that it would be tedious to transfer between p
On Mon, Apr 7, 2008 at 8:04 PM, Terry Reedy <[EMAIL PROTECTED]> wrote:
> Should print() have an option to convert with repr instead of str?
I don't think so -- just write the repr() call. Or write
print(*map(repr, (a, b, c)))
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
On Mon, Apr 7, 2008 at 6:50 PM, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > what do people think of making the str() of a class
> > return just the thing between '...' in the repr()?
>
> Are you talking about the class itself, or instances
> of the class?
No, the class
"Greg Ewing" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| Terry Reedy wrote:
|
| > As in
| >
| print(type(3))
| >
| > int # instead of
|
| I have the same feeling there -- the only time I'm
| likely to be deliberately printing a class is for
| debugging, and then I want una
On Mon, Apr 7, 2008 at 8:40 PM, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > Huh? We do that all the time. We won't let you control when memory is
> > deallocated.
>
> I hardly think that being able to kill threads is
> anywhere near as dangerous as being able to scribble
Guido van Rossum wrote:
> Maybe it should be a forked subprocess then, if it doesn't touch
> anything shared?
It might be taking and returning large data structures
that it would be tedious to transfer between processes.
Pickling them might not be straightforward if they
contain references to obj
Terry Reedy wrote:
> As in
>
print(type(3))
>
> int # instead of
I have the same feeling there -- the only time I'm
likely to be deliberately printing a class is for
debugging, and then I want unambiguity.
--
Greg
___
Python-3000 mailing list
Guido van Rossum wrote:
> what do people think of making the str() of a class
> return just the thing between '...' in the repr()?
Are you talking about the class itself, or instances
of the class?
If the latter, I'm not sure I like that idea. Very
often I write thing like 'print "foo =", foo' as
[catching up on old threads]
On Tue, Mar 18, 2008 at 5:47 PM, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Adam Olsen wrote:
> > I'd tend to assume only *purely* functional languages should have
> > asynchronous interrupts. Any imperative language with them is
> > suspect.
>
> Yet there are situat
On Mon, Apr 7, 2008 at 6:19 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> On Mon, Apr 7, 2008 at 3:04 PM, Benjamin Peterson
> <[EMAIL PROTECTED]> wrote:
> > On Mon, Apr 7, 2008 at 4:45 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > > -0.5 from me. For half of the names that the PEP propo
On Mon, Apr 7, 2008 at 3:04 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> On Mon, Apr 7, 2008 at 4:45 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > -0.5 from me. For half of the names that the PEP proposes to move most
> > users wouldn't be able to guess in which module to find them.
>
On Mon, Apr 7, 2008 at 10:11 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 7, 2008 at 6:11 AM, Antoine Pitrou <[EMAIL PROTECTED]>
> wrote:
> > Gregory P. Smith krypto.org> writes:
> > >
> > > yes bytearray makes more sense to me given that its hard to read into
> an
> > immutab
Guido van Rossum wrote:
> Benjamin Peterson wrote:
> > After a long conversation on the stdlib-sig list, I'd like to
> > bring this before you. For those of you not on the peps mailing
> > list, Guido has expressed lukewarmness (well -0.5) to the idea.
> > However, I'd still like your comments on m
On Mon, Apr 7, 2008 at 4:45 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> -0.5 from me. For half of the names that the PEP proposes to move most
> users wouldn't be able to guess in which module to find them.
>
If they're in *one* (maybe two; we'll see.) other module, it'd be hard to
guess whe
-0.5 from me. For half of the names that the PEP proposes to move most
users wouldn't be able to guess in which module to find them.
On Mon, Apr 7, 2008 at 2:41 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Benjamin Peterson wrote:
> > After a long conversation on the stdlib-sig list, I'd like to
Benjamin Peterson wrote:
> After a long conversation on the stdlib-sig list, I'd like to bring this
> before you. For those of you not on the peps mailing list, Guido has
> expressed lukewarmness (well -0.5) to the idea. However, I'd still like
> your comments on my first PEP.
+1 from me.
> Th
After a long conversation on the stdlib-sig list, I'd like to bring this
before you. For those of you not on the peps mailing list, Guido has
expressed lukewarmness (well -0.5) to the idea. However, I'd still like your
comments on my first PEP.
PEP: XXX
Title: Cleaning out sys and the "interpreter
"Guido van Rossum" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
|> Could not find this in tracker, so http://bugs.python.org/issue2565
|
| And thanks to Martin for making it so.
|
| As a follow-up, what do people think of making the str() of a class
| return just the thing between
> Could not find this in tracker, so http://bugs.python.org/issue2565
And thanks to Martin for making it so.
As a follow-up, what do people think of making the str() of a class
return just the thing between '...' in the repr()? This is much
shorter and in many cases enough.
(This actually inver
Right, this doesn't apply to py3k files at all. (Not that py3k files
are all that thead-safe. :-)
On Mon, Apr 7, 2008 at 8:42 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> gregory.p.smith schrieb:
>
> > Author: gregory.p.smith
> > Date: Mon Apr 7 01:11:17 2008
> > New Revision: 62195
> >
>
gregory.p.smith schrieb:
> Author: gregory.p.smith
> Date: Mon Apr 7 01:11:17 2008
> New Revision: 62195
>
> Modified:
>python/trunk/Doc/c-api/file.rst
>python/trunk/Include/fileobject.h
>python/trunk/Lib/test/test_file.py
>python/trunk/Misc/NEWS
>python/trunk/Objects/fileobje
On Mon, Apr 7, 2008 at 6:11 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
> Gregory P. Smith krypto.org> writes:
> >
> > yes bytearray makes more sense to me given that its hard to read into an
> immutable bytes object ;)
>
> It seems to me that readinto accepts any object providing a writeabl
Gregory P. Smith krypto.org> writes:
>
> yes bytearray makes more sense to me given that its hard to read into an
immutable bytes object ;)
It seems to me that readinto accepts any object providing a writeable buffer
interface. I don't know how to express that as an annotation, though.
__
On Mon, Apr 7, 2008 at 2:00 AM, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> yes bytearray makes more sense to me given that its hard to read into an
> immutable bytes object ;)
Not so hard: http://bugs.python.org/issue2538
Some time ago, bytes were mutable...
--
Amaury Forgeot d'Arc
__
26 matches
Mail list logo