Anyone have an opinion on http://bugs.python.org/issue3492 in regards
to it being a release blocker?
The gist of it: zlib returns bytearrays where other modules return
bytes. zipimport, because it uses zlib, required bytearrays instead
of bytes as input. A few other modules also appear to retur
On Thu, Sep 4, 2008 at 8:39 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Jesus Cea wrote:
>>
>> I would rather revert to the method style, or redo the class to avoid
>> new attribute creation, maybe via some "thread.__setattr__()" magic.
>
> Or maybe with __slots__ in the threading class. It'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregory P. Smith wrote:
> Anyone have an opinion on http://bugs.python.org/issue3492 in regards
> to it being a release blocker?
>
> The gist of it: zlib returns bytearrays where other modules return
> bytes. zipimport, because it uses zlib, require
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Coghlan wrote:
> Guido van Rossum wrote:
>> On Thu, Sep 4, 2008 at 8:47 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>>> Jesus Cea jcea.es> writes:
First we had "thread.setDaemon()". This was not PEP8, so Python 3.0
renamed it to "thre
On Fri, Sep 5, 2008 at 12:10 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nick Coghlan wrote:
>> Guido van Rossum wrote:
>>> On Thu, Sep 4, 2008 at 8:47 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
Jesus Cea jcea.es> writes:
> First we ha
On Fri, Sep 5, 2008 at 12:10 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nick Coghlan wrote:
>> Guido van Rossum wrote:
>>> On Thu, Sep 4, 2008 at 8:47 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
Jesus Cea jcea.es> writes:
> First we ha
This needs to be fixed. It is surely a relic from the alpha1 situation
where the bytes type was mutable. No read APIs should return mutable
bytes. Write APIs should accept mutable and immutable bytes though.
On Fri, Sep 5, 2008 at 12:17 AM, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> Anyone have
I don't know if this is too late to do before the final release, but shouldn't
the implementation of PyUnicodeObject be updated to match the much more
efficient old PyStringObject layout? I mean eliminating the double malloc
that is currently required for each unicode string.
PyStringObject is
This is an excellent idea that fell by the wayside. Since it is a
major coding project there's no way it can be done for 3.0 -- the risk
of introducing new instabilities or leaks is just too high. We *might*
be able to get it in for 3.0.1, if the code is reviewed really well.
Though it might be saf
Jesse Noller wrote:
> On Fri, Sep 5, 2008 at 12:10 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Nick Coghlan wrote:
>>> Hmm, having (daemon=False) as a parameter on start() would probably be
>>> an even better API than having it on __init__() (m
On Fri, Sep 5, 2008 at 10:38 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Jesse Noller wrote:
>> On Fri, Sep 5, 2008 at 12:10 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Nick Coghlan wrote:
Hmm, having (daemon=False) as a parameter on
11 matches
Mail list logo
