Patch / Bug Summary
___
Patches : 342 open ( +3) / 2923 closed ( +1) / 3265 total ( +4)
Bugs: 908 open ( +5) / 5232 closed (+10) / 6140 total (+15)
RFE : 188 open ( +1) / 185 closed ( +1) / 373 total ( +2)
New / Reopened Patches
__
String fo
Phillip J. Eby wrote:
> Just an FYI; Pyrex certainly makes it relatively painless to write code
> that interfaces with C, but it doesn't do much for performance, and
> naively-written Pyrex code can actually be slower than
> carefully-optimized Python code. So, for existing modules that were
Guido van Rossum wrote:
> How stable is Pyrex? Would you be willing to integrate it thoroughly
> with the Python source tree, to the point of contributing the code to
> the PSF? (Without giving up ownership or responsibility for its
> maintenance.)
It's reasonably stable now, I think, although so
> "Guido" == Guido van Rossum <[EMAIL PROTECTED]> writes:
Guido>
Guido> In a different thread I mentioned a design principle for
Guido> which I have no catchy name, but which has often helped me
Guido> design better APIs. One way to state it is to say that
Guido> instead
(sorry for the delayed reply; vacation)
On Aug 14, 2005, at 12:27 PM, Guido van Rossum wrote:
On 8/14/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
Wilfredo S
ánchez Vega <[EMAIL PROTECTED]> writes:
I'm curious about why Python lacks FileNotFoundError,
PermissionError and the li
On Sep 7, 2005, at 7:11 AM, Guido van Rossum wrote:
> On 9/7/05, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>
>> On Wed, 2005-09-07 at 05:23, Stephen J. Turnbull wrote:
>>
>>
>>> But print-ng looks
>>> like becoming the OOWTDI for a lot of applications. IMO it's
>>> just too
>>> early to give up
Christopher Armstrong <[EMAIL PROTECTED]> wrote:
> On 9/7/05, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> > Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > > On 9/6/05, Greg Ewing <[EMAIL PROTECTED]> wrote:
> > > > A better plan would be to build something akin to
> > > > Pyrex into the scheme of
Fred L. Drake, Jr. wrote:
> It would be good to have more specific guidelines for documentation.
Would it be possible to have each item in the documentation start out by
auto quoting that items __doc__ string?
Then omissions, errors, and contradictions would be easy to find and the
full docume
On 9/7/05, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-09-07 at 05:23, Stephen J. Turnbull wrote:
>
> > But print-ng looks
> > like becoming the OOWTDI for a lot of applications. IMO it's just too
> > early to give up on print-ng becoming the one obvious way to do it for
> > a lot of i
Nick Coghlan wrote:
> I found the following to be an interesting experiment:
>
> -
> from string import Template
>
> def format(*args, **kwds):
> fmt = args[0]
> kwds.update(("p%s" % idx, arg) for idx, arg in enumerate(args))
> return Template(fmt).substitute(*
Barry Warsaw wrote:
> On Wed, 2005-09-07 at 05:23, Stephen J. Turnbull wrote:
>
>
>>But print-ng looks
>>like becoming the OOWTDI for a lot of applications. IMO it's just too
>>early to give up on print-ng becoming the one obvious way to do it for
>>a lot of i18n apps, too.
>
>
> +1. I have a
On 9/6/05, Steven Bethard <[EMAIL PROTECTED]> wrote:
> I'd also prefer something along the lines of Fredrik's suggestion, but
> I don't write enough C code to understand Paul's last point. Could
> someone briefly explain why mixins wouldn't work in C code?
I had in mind "it would be complicated a
On Wed, 2005-09-07 at 05:23, Stephen J. Turnbull wrote:
> But print-ng looks
> like becoming the OOWTDI for a lot of applications. IMO it's just too
> early to give up on print-ng becoming the one obvious way to do it for
> a lot of i18n apps, too.
+1. I have a gut feeling that we can make it e
On 9/7/05, Josiah Carlson <[EMAIL PROTECTED]> wrote:
>
> Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 9/6/05, Greg Ewing <[EMAIL PROTECTED]> wrote:
> > > A better plan would be to build something akin to
> > > Pyrex into the scheme of things, so that all the
> > > refcount/GC issues are take
On Wed, Sep 07, 2005 at 02:01:01AM -0400, Phillip J. Eby wrote:
[...]
> Just an FYI; Pyrex certainly makes it relatively painless to write code
> that interfaces with C, but it doesn't do much for performance, and
> naively-written Pyrex code can actually be slower than carefully-optimized
> Pyt
> "Guido" == Guido van Rossum <[EMAIL PROTECTED]> writes:
Guido> Sure, we must provide good i18n support. But the burden on
Guido> users who don't need i18n should be negligeable; they
Guido> shouldn't have to type or know extra stuff that only exists
Guido> for the needs of i1
Collin Winter wrote:
> Am 31-Aug 05, Charles Cazabon <[EMAIL PROTECTED]> schrieb:
>
>
>>Perhaps py3k could have a py2compat module. Importing it could have the
>>effect of (for instance) putting compile, id, and intern into the global
>>namespace, making print an alias for writeln, alias the sta
Fredrik Lundh wrote:
> Josiah Carlson wrote:
>
>>Perhaps a bit into the future, extending import semantics to notice .pyx
>>files, compare their checksum against a stored md5 in the compiled
>>.pyd/.so, and automatically recompiling them if they (or their includes)
>>have changed: +10 (I end up do
Josiah Carlson wrote:
> Perhaps a bit into the future, extending import semantics to notice .pyx
> files, compare their checksum against a stored md5 in the compiled
> .pyd/.so, and automatically recompiling them if they (or their includes)
> have changed: +10 (I end up doing this kind of thing by
Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 9/6/05, Greg Ewing <[EMAIL PROTECTED]> wrote:
> > A better plan would be to build something akin to
> > Pyrex into the scheme of things, so that all the
> > refcount/GC issues are taken care of automatically.
>
> That sounds exciting. I have to adm
Greg Ewing <[EMAIL PROTECTED]> writes:
> Guido van Rossum wrote:
>
>>>While we're on the subject of Python 3000, what's the
>>>chance that reference counting when calling C
>>>functions from Python will go away?
>>
>> We'd have to completely change the implementation. We're not
>> planning on tha
21 matches
Mail list logo
