Martin v. Löwis wrote:
>>> Can you explain this a bit more? I presume you're talking about
>>> subclassing in C
>> Yes, I mentioned Cython above.
>
> Can you please still elaborate? I have never used Cython before
Should have been clearer, sorry. C-level subtyping in Cython/Pyrex works as
follows
Hi Gregory,
If you need help in testing out the bytearray related patches
on various platforms (#3797, #3492) let me know.
Regards
--Anand
On Sun, Sep 7, 2008 at 2:23 AM, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> issue 3797 created with trivial patches for the remaining bytearray
>
> Given that you can, today, subclass str in Python, without wasting an
> extra 4/8 bytes of memory, or adding anything new to the class object,
> why wouldn't anyone who really wanted to make a hypothetical optimized
> subclass just use the same mechanism (putting your additional data
> *after* th
>> Can you explain this a bit more? I presume you're talking about
>> subclassing in C
>
> Yes, I mentioned Cython above.
Can you please still elaborate? I have never used Cython before, but
if it cannot efficiently subclass str, isn't that a bug in Cython?
>> I do note that the mechanisms that
> On Windows, none are available except dbm.dumb and bsddb (presently).
> If bsddb is to be removed, can/should one of the other "real" dbm
> variants be added to the standard binary, so that Windows users have
> at least one usable dbm option?
Which one specifically? What's the licensing implicat
On Sat, Sep 6, 2008 at 8:14 AM, Jesse Noller <[EMAIL PROTECTED]> wrote:
> 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
>> Barry Warsaw wrote:
>>> I'm not going to release rc1 tonight.
>>> I'd like to try again on Friday and stick to rc2 on the 17th.
>
> There are 8 open release blockers, a few of which have patches that need
> review. So I think we are still not ready to release rc1. But it worries
> me because I
On Sep 7, 2008, at 6:55 PM, Guido van Rossum wrote:
One possibility that occurs to me is to use a PyVarObject variant
that
allocates space for an additional void pointer before the variable
sized
section of the object. The builtin type would leave that pointer
NULL,
but subtypes could perfor
On Sun, Sep 7, 2008 at 2:23 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
>> All in all, given the advantage (half the number of allocations) of
>> the proposal I think there would have to be *very* good arguments
>> against before we reject this outright. I'd like to unders
Brett Cannon wrote:
> On Sun, Sep 7, 2008 at 8:22 AM, <[EMAIL PROTECTED]> wrote:
>> I created this bug report against 3.0 yesterday:
>>
>>http://bugs.python.org/issue3799
>>
>> I marked it high priority because it seems to me that all the dbm.* modules
>> should agree on whether they accept st
Guido van Rossum wrote:
> All in all, given the advantage (half the number of allocations) of
> the proposal I think there would have to be *very* good arguments
> against before we reject this outright. I'd like to understand
> Marc-Andre's reasons too.
As Stefan notes, because of the frequency w
On Sun, Sep 7, 2008 at 8:22 AM, <[EMAIL PROTECTED]> wrote:
> I created this bug report against 3.0 yesterday:
>
>http://bugs.python.org/issue3799
>
> I marked it high priority because it seems to me that all the dbm.* modules
> should agree on whether they accept strings as keys or require byt
On Sat, Sep 6, 2008 at 7:33 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
[SNIP]
> So the standard library packages would be self-contained by default, but
> an application could explicitly request that the extensible packages be
> expanded to incorporate other directories.
>
I was thinking about th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 7, 2008, at 10:51 AM, Fredrik Lundh wrote:
Barry Warsaw wrote:
I'm not going to release rc1 tonight. There are too many open
release blockers that I don't want to defer, and I'd like the
buildbots to churn through the bsddb removal on a
>> Parsing Unicode XML strings isn't quite that meaningful.
>
> Maybe not according to the XML standard, but I can see lots of
> practical situations where the encoding is always known and applied by
> some other layer, i.e. the I/O library or a database wrapper. Forcing
> XML to be interpreted as
I created this bug report against 3.0 yesterday:
http://bugs.python.org/issue3799
I marked it high priority because it seems to me that all the dbm.* modules
should agree on whether they accept strings as keys or require bytes.
That's clearly not the case at the moment. I suppose perhaps I s
Hi,
Guido van Rossum wrote:
> On Sun, Sep 7, 2008 at 12:15 AM, Stefan Behnel <[EMAIL PROTECTED]> wrote:
>> Antoine Pitrou wrote:
>>> Also note that Marc-André Lemburg (one of the authors of the unicode
>>> implementation) is opposed to that change. See the discussion in the bug
>>> tracker
>>> is
Antoine Pitrou wrote:
> Stefan Behnel behnel.de> writes:
>> From a Cython perspective, I find the lack of efficient subclassing after
>> such
>> a change particularly striking. That seriously bit me in Py2 when I tried
>> making XML text content a bit more intelligent in lxml (i.e. make it rememb
On Sun, Sep 7, 2008 at 12:15 AM, Stefan Behnel <[EMAIL PROTECTED]> wrote:
> Antoine Pitrou wrote:
>> Also note that Marc-André Lemburg (one of the authors of the unicode
>> implementation) is opposed to that change. See the discussion in the bug
>> tracker
>> issue for the details.
>
> From a Cyth
Stefan Behnel behnel.de> writes:
>
> From a Cython perspective, I find the lack of efficient subclassing after such
> a change particularly striking. That seriously bit me in Py2 when I tried
> making XML text content a bit more intelligent in lxml (i.e. make it remember
> what XML element it ori
Antoine Pitrou wrote:
> Also note that Marc-André Lemburg (one of the authors of the unicode
> implementation) is opposed to that change. See the discussion in the bug
> tracker
> issue for the details.
From a Cython perspective, I find the lack of efficient subclassing after such
a change partic
21 matches
Mail list logo
