Terry Reedy wrote:
| But in the case of builtin function, it can't work.
What is it that 'cannot work'? My guess is that you are talking about the
fact that instances do not get bound as an argument to the first parameter
of a builtin.
Yes, this is what Haoyu was talking about - I suspect h
Terry Reedy wrote:
What is it that 'cannot work'? My guess is that you are talking about the
fact that instances do not get bound as an argument to the first parameter
of a builtin.
Yes, this is what I means. Sorry if my words confused you.
If *extension* function show a difference, perh
Richard Boulton wrote:
Yes, this is what Haoyu was talking about - I suspect he meant "doesn't
work" rather than "cannot work", and that's the reason it doesn't work
(both in 2.x and 3.0).
Thanks Richard for helping me to explain.
I'll ask a direct question: what is the recommended replacemen
Hi,
I started working on this ticket but I'm going to need some
clarifications, it's called "Adapt pydoc to new doc system" and says
only "so that this doesn't get lost":
http://bugs.python.org/issue1883
Can someone give more directions on what really needs to be done?
Thanks in adv
Humberto Diogenes schrieb:
Hi,
I started working on this ticket but I'm going to need some
clarifications, it's called "Adapt pydoc to new doc system" and says
only "so that this doesn't get lost":
http://bugs.python.org/issue1883
Can someone give more directions on what really ne
On 28/04/2008, at 10:15, Georg Brandl wrote:
Humberto Diogenes schrieb:
http://bugs.python.org/issue1883
Can someone give more directions on what really needs to be done?
Hehe, this was mainly meant as a reminder item for me since the URLs
for pydoc to refer to HTML documentation will ch
On Mon, Apr 28, 2008 at 4:14 AM, Haoyu Bai <[EMAIL PROTECTED]> wrote:
...
> Yes, these are the very problems I encountered. I think the using of
> "new.instancemethod" is for speed, because in SWIG's command line, the
> "-fastproxy" option enabled it:
>
> -fastproxy - Use fast proxy mecha
Haoyu Bai schrieb:
> I know this is not a bug, but however it is an exception in the
> language, what Python trying to avoid.
>
> Since all C function in extension module is treated as builtin function
> or method, the problem maybe bigger than it looks like. In the SWIG's
> case, it originally us
On Sun, Apr 27, 2008 at 4:07 AM, Alexander Belopolsky
<[EMAIL PROTECTED]> wrote:
> On Sat, Apr 26, 2008 at 2:49 PM, Facundo Batista
> <[EMAIL PROTECTED]> wrote:
>
>
> > Which should the range() definition be, in your words?
>
> In terms of ABCs, range(..) is a Sized Iterable in the current
> i
BTW, if you're looking for a term describing range() that's better
than set or sequence, how about "series"? It's a mathematical word
that matches pretty exactly. (More accurately, I believe it's an
algebraic series.)
On Mon, Apr 28, 2008 at 4:18 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> O
Alex Martelli wrote:
Is this a SWIG-specific issue (so
that SWIG can take care of it in the C code it generates or links) or
sufficiently general to warrant an addition to the Python core?
I haven't been following this closely, but if the issue is what
I think it is, Pyrex is going to have the
It seems that os.walk has more options and a cleaner interface to
walking trees than os.path.walk does. Is there support for the removal
this in Py3k?
--
Cheers,
Benjamin Peterson
___
Python-3000 mailing list
[email protected]
http://mail.python.or
[bcc to stdlib-sig]
After two false starts over the YEARS of trying to cleanup and
reorganize the stdlib, creating a SIG to get this going, having Guido
give the PEP the once-over over the past several days, and creating
two new bugs reports (issues 2715 and 2716), PEP 3108 is finally ready
for pu
"Guido van Rossum" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| BTW, if you're looking for a term describing range() that's better
| than set or sequence, how about "series"? It's a mathematical word
| that matches pretty exactly. (More accurately, I believe it's an
| algebraic s
Brett Cannon wrote:
> Subject: [Python-3000] PEP 3108 - stdlib reorg/cleanup
>
> [bcc to stdlib-sig]
>
> After two false starts over the YEARS of trying to cleanup and
> reorganize the stdlib, creating a SIG to get this going, having Guido
> give the PEP the once-over over the past several days,
+1
-- Talin
___
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
A few comments:
Intro to delete: could point out here that anyone who really wants a
deleted module can/should update it to work with 3.0 and make available
through PyPI.
-
obsolete/popen2 ... "replaces them."
'them' should be 'it': any other popenx modules seem to be gone
alread
Nice job, Brett. I only have two concerns:
As you don't quite note, the Mac "ic" module is the interface to the
"Internet Configuration" system on the Mac. In particular, it's where
proxy information is drawn from. We need to have that replacement
code in hand before "ic" is jettisoned. You al
On Mon, Apr 28, 2008 at 8:39 PM, Bill Janssen <[EMAIL PROTECTED]> wrote:
> Nice job, Brett. I only have two concerns:
>
> As you don't quite note, the Mac "ic" module is the interface to the
> "Internet Configuration" system on the Mac. In particular, it's where
> proxy information is drawn fr
On Mon, Apr 28, 2008 at 8:39 PM, Terry Reedy <[EMAIL PROTECTED]> wrote:
> A few comments:
>
> Intro to delete: could point out here that anyone who really wants a
> deleted module can/should update it to work with 3.0 and make available
> through PyPI.
Guido and I discussed this and he pointed
On Mon, Apr 28, 2008 at 10:18:41PM -0700, Brett Cannon wrote:
> On Mon, Apr 28, 2008 at 8:39 PM, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > Nice job, Brett. I only have two concerns:
> >
> > As you don't quite note, the Mac "ic" module is the interface to the
> > "Internet Configuration" system
On Mon, Apr 28, 2008 at 8:30 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> * sched
>
> + Replaced by threading.Timer.
I don't see sched as obsoleted by threading.Timer. It's much simpler
to use (no need for locking) and more efficient (no legions of
sleeping threads). Instead, maybe it should
22 matches
Mail list logo
